Re: [Pulp-dev] RPM stories, feedback is needed

2020-01-27 Thread Justin Sherrill

Both of these look good to me

Justin

On 1/27/20 2:44 PM, Tatiana Tereshchenko wrote:

I'm looking for feedback on the stories below.  For both:
 - is the logic correct or if anything is missing?
 - where to store info (from a remote) which is needed later?

1. https://pulp.plan.io/issues/4458 As a user, I can configure which 
checksum algorithm to use when creating metadata
 - the suggestion is to store a checksum type of a remote on a rpm 
repo version model.


2. https://pulp.plan.io/issues/6055 As a user, my sync is not 
operational if there are no changes
  - the suggestion is to store all the necessary details on a 
rpm repository model.


Please comment on the issues (preferred) or discuss here.

Thank you,
Tanya

___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev


[Pulp-dev] RPM stories, feedback is needed

2020-01-27 Thread Tatiana Tereshchenko
I'm looking for feedback on the stories below.  For both:
 - is the logic correct or if anything is missing?
 - where to store info (from a remote) which is needed later?

1. https://pulp.plan.io/issues/4458 As a user, I can configure which
checksum algorithm to use when creating metadata
 - the suggestion is to store a checksum type of a remote on a rpm repo
version model.

2. https://pulp.plan.io/issues/6055 As a user, my sync is not operational
if there are no changes
  - the suggestion is to store all the necessary details on a
rpm repository model.

Please comment on the issues (preferred) or discuss here.

Thank you,
Tanya
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev