Project

Profile

Help

Task #2863

Align existing code base with publisher attributes from the MVP

Added by amacdona@redhat.com over 2 years ago. Updated 6 months ago.

Status:
CLOSED - COMPLETE
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 23

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.


Checklist


Related issues

Copied from Pulp - Task #2818: Align existing code base with importer attributes from the MVP MODIFIED Actions

History

#1 Updated by amacdona@redhat.com over 2 years ago

  • Copied from Task #2818: Align existing code base with importer attributes from the MVP added

#2 Updated by dkliban@redhat.com over 2 years ago

  • Groomed changed from No to Yes

#3 Updated by amacdona@redhat.com over 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to amacdona@redhat.com

#4 Updated by amacdona@redhat.com over 2 years ago

  • Status changed from ASSIGNED to NEW
  • Assignee deleted (amacdona@redhat.com)

#5 Updated by bizhang over 2 years ago

  • Tags Pulp 3 Plugin Writer Alpha added

#6 Updated by mhrivnak about 2 years ago

  • Priority changed from Normal to High

#7 Updated by mhrivnak about 2 years ago

  • Sprint/Milestone set to 42

#8 Updated by ttereshc about 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to ttereshc

#9 Updated by ttereshc about 2 years ago

  • 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.

#10 Updated by bmbouter about 2 years ago

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?

#11 Updated by mhrivnak about 2 years ago

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.

#12 Updated by bmbouter almost 2 years ago

  • Tags deleted (Pulp 3 Plugin Writer Alpha)

Cleaning up Redmine tags

#13 Updated by bmbouter over 1 year ago

  • Sprint set to Sprint 23

#14 Updated by bmbouter over 1 year ago

  • Sprint/Milestone deleted (42)

#15 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#16 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF