openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #23093
release process and sample configs
Hi All,
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
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.
Thanks
Darren
Follow ups