First let me say, thank you Nick for setting this up, user-facing
release notes have been sorely lacking.
Excerpts from Nick Coghlan's message of 2013-02-13 15:28:31 +1000:
The process is fairly simple: if you're making a user/admin
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.
How does this fit in with the existing practice of putting admin upgrade
instructions into SchemaUpgrades/ (which get packaged in
Do we drop the SchemaUpgrades/ stuff entirely, and use What's New for
upgrade instructions also?
Does that mean it will end up with blobs of SQL all through it, like the
SchemaUpgrades notes currently have?
What about the (admittedly rare) occasions when we have a Python script
for doing data migration/fixing as part of an upgrade?
Dan Callaghan <dcallagh(a)redhat.com>
Software Engineer, Infrastructure Engineering and Development
Red Hat, Inc.