[openstack-dev] [Nova] The unbearable lightness of specs
joe.gordon0 at gmail.com
Wed Jun 24 21:41:12 UTC 2015
On Wed, Jun 24, 2015 at 10:04 AM, Ed Leafe <ed at leafe.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> On 06/24/2015 08:38 AM, Nikola Đipanov wrote:
> > I urge people to reply to this instead of my original email as the
> > writing is more detailed and balanced.
> OK, I've read what others have written, and want to throw in my own
> 0.00008316 BTC.
> The spec process is invaluable, but that is not to say that it can't be
> improved - a *lot*.
> Other emails have touched on the biggest disconnect in the process: that
> an approved spec magically becomes unapproved on a particular calendar
> date. This makes no sense whatsoever. If it was a good idea yesterday,
> it will almost always be a good idea tomorrow.
I don' think this is a accurate summary of the status quo.
We currently have the fast track process, where if a spec was previously
approved we will quickly re-approve it. (I do a git diff between the
previous version and make sure the diff is trivial). By my count in liberty
we successfully used this procedure around 14 times. So yes things do
magically become unapproved on a somewhat random date, but I don't think
this is realistically a major pain point. (Side note we were able to
approve a lot of those specs before the summit).
Secondly nova is moves fast. For example in Kilo we had: 4752 files
changed, 299,275 insertions(+), 309,689 deletions(-) . What is amazing
about this is nova kilo only had 251,965 lines . So specs that we
approved 6 months ago are often not valid anymore, I have seen this happen
time and time again.
 git diff --stat 0358c9afb5af6697be88b5b69d96096a59a2148e
 git ls-files | xargs wc -l
> The other obvious disconnect is the gap between nova-core and
> nova-spec-core. If someone is knowledgeable enough and trusted enough to
> commit code to Nova, they should be trusted to approve a spec.
> Those two changes aren't controversial, are they? If not, let's do them
> ASAP, and then iterate from there.
> - --
> - -- Ed Leafe
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> Comment: GPGTools - https://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> -----END PGP SIGNATURE-----
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev