Task #2863
closed
Align existing code base with publisher attributes from the MVP
Description
In our MVP call today , we altered the language that describes publisher fields. This task is to align the code to what we discussed.
Check the repositories section of the MVP page for up to date language.
- Copied from Task #2818: Align existing code base with importer attributes from the MVP added
- Groomed changed from No to Yes
- Status changed from NEW to ASSIGNED
- Assignee set to amacdona@redhat.com
- Status changed from ASSIGNED to NEW
- Assignee deleted (
amacdona@redhat.com)
- Tags Pulp 3 Plugin Writer Alpha added
- Priority changed from Normal to High
- Sprint/Milestone set to 42
- Status changed from NEW to ASSIGNED
- Assignee set to ttereshc
- Status changed from ASSIGNED to CLOSED - COMPLETE
- % Done changed from 0 to 100
Publisher model/serializer is correct and complaint with the discussed Publisher attributes for MVP, no changes needed.
Additional attribute auto_publish exists on the model/serializer.
It was suggested to discuss a need for auto_publish functionality in MVP after alpha release.
If auto_publish is not finalized can we remove it for now. Then we we are sure of it's future we can bring it back. Does that sound OK?
I think we are close to finalizing it and just need to discuss it a touch further. Jeff and I agreed so far that auto-publish makes sense to keep and is trivial to use.
We could try to get it added to the MVP, which would then make it clear. But the MVP is of course a minimum, and nothing stops us from strategically including additional things where they make sense. So we could just leave this in and use it.
Either way, let's keep it for now and discuss as necessary.
- Tags deleted (
Pulp 3 Plugin Writer Alpha)
- Sprint/Milestone deleted (
42)
- Sprint/Milestone set to 3.0.0
Also available in: Atom
PDF
.