On Tue, Dec 15, 2015 at 04:46:02PM +0100, Micha?? Dulko wrote: > On 12/15/2015 04:08 PM, Ryan Rossiter wrote: > > Thanks for the review Michal! As for the bp/bug report, there???s four > > options: > > > > 1. Tack the work on as part of bp cinder-objects > > 2. Make a new blueprint (bp cinder???object-fields) > > 3. Open a bug to handle all changes for enums/fields > > 4. Open a bug for each changed enum/field > > > > Personally, I???m partial to #1, but #2 is better if you want to track this > > work separately from the other objects work. I don???t think we should go > > with bug reports because #3 will be a lot of Partial-Bug and #4 will be > > kinda spammy. I don???t know what the spec process is in Cinder compared to > > Nova, but this is nowhere near enough work to be spec-worthy. > > > > If this is something you or others think should be discussed in a meeting, > > I can tack it on to the agenda for tomorrow. > > bp/cinder-object topic is a little crowded with patches and it tracks > mostly rolling-upgrades-related stuff. This is more of a refactoring > than a ovo essential change, so simple specless bp/cinder-object-fields > is totally fine to me.
I agree. If you can file a new blueprint for this, I can approve it right away. That will help track the effort. Thanks for working on this! Sean (smcginnis) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
