The Goldfish Chronicles

I’m starting to turn into a nomadic open source release catalyst. At least for the last few months. This is because my colleagues and I are deciding on stable versions that will form the core support versions for the next 9 months and it’s nicer to make a release happen at the source than do lots of backports.

Now that lots of Commons releases are done (DBCP 1.2.2 and Logging 1.1.1 still need to happen), the next on my list is Quartz 1.6.1 and I get to try out my belief that a non-committer can enact change. Here’s how I tell people to do this in Commons when they ask on commons-dev@:

1. If you’re not sure if another release is warranted, ask on the mailing list - ie: some components are done
2. Create patches in the JIRA
3. Put together a release plan on the wiki
4. Bring the subject up on the mailing list
5. Loop over: Wait for activity, get involved, remind the list of the plan
6. Release! (?)

Currently it bodes well for Quartz 1.6.1. I’ve followed the above list and put together a release plan on their wiki and have applied patches to many of the issues over the last month or so. More importantly, the committers have a theme for the release (minor bugfix release) which helps to focus the activity.

This entry was posted on Sunday, March 11th, 2007 at 7:55 pm and is filed under Tech. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.