[nova] "future" specs and blueprints
smooney at redhat.com
Fri Mar 29 11:04:01 UTC 2019
On Thu, 2019-03-28 at 16:28 -0500, Ed Leafe wrote:
> On Mar 28, 2019, at 4:02 PM, Michael Still <mikal at stillhq.com> wrote:
> > I think the problem the backlog directory solves is that it gives core a way to give a soft no that makes
> > contributors less upset. I don't see a lot of value in that though. If the spec is a no then just say no. If its a
> > big enough problem for the proposer they can hold their own patches or fork nova, much as people such as StarlingX,
> > HP, and Rackspace Public Cloud did back in the day.
> IIRC, the backlog was for when people had an idea for a feature or improvement that had already been discussed and
> decided that it was potentially worthwhile, but was not going to be done in the current cycle. The benefit over
> putting it in the current cycle’s specs was that it didn’t attract reviewers and didn’t dilute the completed/proposed
> spec ratio, which some people were very concerned about. It also gave people a chance to “socialize” the idea without
> having to commit to creating a full spec.
if we submitted code via the mailing list. which i hope we never do... that might be more useful
but given we use gerrit i then to socialise ideas by either submiting a draft spec or writing it up in etherpad
so and then posting to the mailing list or pinging people on irc for input.
> That said, it was never very active and if it were to disappear I don’t think it would make any difference.
effectivly because gerrit reviews live forever, they provide much of the benifit however i do agree that
review can get lost in gerrit and having a backlog of "we should proably do this at some point" reviews might
be useful but people who work upstream across multiple release tend to bring up previous ideas again organically
when we get to a point where its actully pratical to finally implement it. so if the backlog directory was to
disappear i dont think it would have much effect in practice.
with that said i did have a cases recently where
one part of redhat that was not familar with nova sited a spec in our backlog folder as a depedency for a feature we
were requesting, that was until we pointed out to them the spec in question (
https://github.com/openstack/nova-specs/blob/master/specs/backlog/approved/parallel-scheduler.rst) was massively out of
date and the problem descirbed
in this spec is why placement now exits.
looking at our current "backlog" https://github.com/openstack/nova-specs/tree/master/specs/backlog/approved i think they
are all out of date.
> -- Ed Leafe
More information about the openstack-discuss