openstack team mailing list archive

[Thierry Carrez <thierry@xxxxxxxxxxxxx>]

Darren Birkett wrote:
> I've noticed that a lot of the projects do not get their sample configs
> updated as part of the release process.  I'd suggest that one of the
> final commits to each project before a release is cut, is to update the
> sample config so it's relevant to the codebase that's being released and
> packaged.
> 
> For those that aren't aware, in each project there is a script that can
> be run that will parse the entire project tree and extract all options
> cleanly into a new sample config file, so it need not be an onerous task

That's a very good point. This should be done before the first release
candidate is cut -- and tested/refreshed if necessary afterwards. I'll
add it to the release process.

> I also think that the entire sample config should go into the docs for a
> release, so that people (non devs) don't need to hunt around in the
> source code to find the elusive option they want to use.

I'll let Anne comment on that, but it sounds sane to me :)

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack