Last week we agreed[1] to follow that other project in setting up a
specs repo.[2] (Many thanks to Ying, Monty and Clint for getting this up
and running.)
I'm still figuring out myself how this is going to work, but the basic
idea seems to be this:
- All new blueprints should be submitted as Gerrit reviews to the specs
repo. Do NOT submit new blueprints to Launchpad
- Existing blueprints in Launchpad are fine, there's no need to touch them.
- If you need to add design information to an existing blueprint, please
do so by submitting a Gerrit review to the specs repo and linking to it
from Launchpad, instead of using a wiki page.
A script will create Launchpad blueprints from approved specs and
heat-drivers (i.e. the core team) will target them to milestones. Once
this system is up and running, anything not targeted to a milestone will
be subject to getting bumped from the series goal by another script.
(That's why you don't want to create new bps in Launchpad.)
If anybody has questions, I am happy to make up answers.
Let's continue to keep things lightweight. Remember, this is not a tool
to enforce a process, it's a better medium for the communication that's
already happening. As a guide:
- the more ambitious/crazy/weird your idea is, the more detail you need
to communicate.
- the harder it would be to throw part or all of the work away, the
earlier you need to communicate it.
- as always, do whatever you judge best, for whatever definition of
'best' you judge best.
cheers,
Zane.
[1]
http://eavesdrop.openstack.org/meetings/heat/2014/heat.2014-05-21-20.00.html
[2] http://git.openstack.org/cgit/openstack/heat-specs
_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
