Adam Murdoch wrote:
Hans Dockter wrote:
I have a couple of issues regarding our release process.
If we do a minor release we have a Wiki page for the release. This
page describes the new and noteworthy and displays a Jira query with
the fixed issues. What should be do in case of a bug fix release? So
far I have pasted the Jira issues in the announce email. But thinking
about it, I guess we should also have a Wiki page for bug fix
releases. Then there is also one place to look for all release notes.
For the 0.6 and the 0.6.1 release I have forgotten to update the
release notes (changelog.txt) which are shipped with the distribution.
Which shows again that things which are not automated are likely to
fail. There are couple of ways we can deal with this in the future:
- Don't ship a changelog.txt.
- Autogenerate the changelog.txt with a Jira query.
- Just have a link to the wiki release notes in changelog.txt
Thoughts?
I think we should have the same process for all releases - bug fix or
minor or major.
You should start by writing down what one has to do to do a release. A
checklist can be just as reliable and a whole heap cheaper than
automation in some situations. Then we can simplify and automate later,
if we need to.
Adam
I'm new to gradle but I've been working with Maven for a few years. For Maven
(and Mojo) releases we have a checklist [1][2], and I think this works pretty
well. The same process is used for every release, as Adam suggests. IMO the
less you have to think about the detailed steps of the release, the better.
Instead of having a full wiki page for each release, we just update a list of
recent releases on the wiki home page and link to jira [3]. And the wiki page
also picks up the release announcements through rss.
As far as the changelog, if it's easy to autogenerate it from jira then I think
it's worth it. Otherwise I think just a link to jira is fine.
[1]http://maven.apache.org/developers/release/releasing.html
[2]http://mojo.codehaus.org/development/performing-a-release.html
[3]http://docs.codehaus.org/display/MAVEN/Home
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
