Hi!
As you all probably know, we've switched to reno for managing release
notes. What it also means is that the release team has stopped managing
milestones for us. We have to manually open/close milestones in
launchpad, if we feel like. I'm a bit tired of doing it for inspector,
so I'd prefer we stop it. If we need to track release-critical patches,
we usually do it in etherpad anyway. We also have importance fields for
bugs, which can be applied to both important bugs and important features.
During a quick discussion on IRC Sam mentioned that neutron also dropped
using blueprints for tracking features. They only use bugs with RFE tag
and specs. It makes a lot of sense to me to do the same, if we stop
tracking milestones.
For both ironic and ironic-inspector I'd like to get your opinion on the
following suggestions:
1. Stop tracking milestones in launchpad
2. Drop existing milestones to avoid confusion
3. Stop using blueprints and move all active blueprints to bugs with RFE
tags; request a bug URL instead of a blueprint URL in specs.
So in the end we'll end up with bugs for tracking user requests, specs
for complex features and reno for tracking for went into a particular
release.
Important note: if you vote for keeping things for ironic-inspector, I
may ask you to volunteer in helping with them ;)
Dmitry.
__________________________________________________________________________
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
