The new release notes infrastructure has been merged into the develop
branch.
The process is fairly simple: if you're making a user/admin facing
change for 1.0, it must be captured in a reStructuredText file under
"documentation/whats-new/release-1.0/". Any affected patch won't make it
through code review until the release note is present.
Providing technical release notes for "under the hood" stuff (like
replacing SimpleXMLRpcServer on the lab controllers with gevent+flask)
is encouraged, but not required.
The exact formatting and wording of the draft notes isn't a big deal,
the main requirement during development is to make sure that the gist of
any changes is captured in that directory, so that we don't forget to
mention it when preparing the final version of the notes. Using separate
files rather than all updating a single file should help to avoid
spurious merge conflicts on Gerrit.
Once we hit feature freeze in early March, I'll take care of
reformatting the notes with an eye to making them more readable
(splitting them out into admin/user/developer notes, grouping notes for
related features together, etc).
For reference, basic instructions are kept as a comment in:
http://git.beaker-project.org/cgit/beaker/tree/documentation/whats-new/in...
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Python Applications Team Lead
Beaker Development Lead (
http://beaker-project.org/)
PulpDist Development Lead (
http://pulpdist.readthedocs.org)