[Pulp-dev] Roadmaps for plugins
mhrivnak at redhat.com
Tue Oct 17 01:04:01 UTC 2017
That all looks good.
We talked about identifying from a high level what needs to be done to get
a Pulp 3 plugin up to a comparable state to its Pulp 2 predecessor. It's
not necessarily parity, because in some cases we'll want to drop or change
behaviors. Only after the full roadmap is written down would we then decide
where to draw the 3.0 MVP line.
On Mon, Oct 16, 2017 at 4:17 PM, Robin Chan <rchan at redhat.com> wrote:
> During our internal Pulp meeting this year, we discussed creating a
> roadmap for plugins. I would like to capture our discussion and ask for
> feedback so that we can start working on our first few roadmaps for
> plugins. We hope that this will be an iterative approach to planning and
> creating roadmaps, extending it to other plugins or core if they are
> *Why? - What will a roadmap help do?*
> Communicate relative priority of work for a plugin
> Determine MVP (for Pulp 3) for a plugin
> Help identify dependencies on work outside of the plugin
> Capture architectural decisions especially when departing from past Pulp 2
> implementations (was this implied in conversation? writing this out is
> Provide direction with the understanding that work planned farther in
> future is subject to change.
> EPIC level descriptions of work - so not user stories, not tasks, not use
> Describe major functionality delivered in an order
> Use y release descriptions for EPICs
> What did I forget to add? What else would be helpful to add to a roadmap,
> take away, or state that it would be described/accounted for elsewhere?
> Pulp-dev mailing list
> Pulp-dev at redhat.com
Principal Software Engineer, RHCE
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev