The draft release notes page for Beaker 0.12 has been updated to reflect
the current status of the release:
To better assess the readability of the new release notes page, Dan
Callaghan has backfilled a set of release notes for 0.11. When we create
the beaker-0.12 maintenance branch, any changes in the "Unreleased
Changes" section will be edited down into a "What's New in Beaker
document aimed primarily at Beaker users and an "Upgrading to Beaker
0.12" document aimed primarily at administrators of a Beaker instance.
We're definitely interested in feedback on the format of these notes,
since Beaker 0.12 will be the first release to include notes that are
more than just a list of Bugzilla references.
On the developer side, Dan has also created an easier to manage system
where all new release notes are placed in a directory called "next" and
appear in the "Unreleased Changes" section of the release notes page.
This means if a change isn't ready for a given release, we can easily
slide it into the next release without needing to change the destination
directory of the associated release note.
P.S. We're aware that the draft docs for 0.12 currently still claim to
be for Beaker 0.11. Unfortunately, this is a quirk of our current
release process which isn't particularly easy to change. It annoys us
too, but it's not clear when we'll get it fixed - until it is, the "in
development" docs will claim to be for the previous release (aside from
the big warning at the top of each page).
Red Hat Infrastructure Engineering & Development, Brisbane
Python Applications Team Lead
Beaker Development Lead (http://beaker-project.org/
PulpDist Development Lead (http://pulpdist.readthedocs.org