I have access to hudson :)
Great! And James just got approved as a committer, so he should have access too. Wrt. the cherry picking, it's a tad annoying that it's so manual. Would be nice to start tagging merges with which release they should be a part of and then write a script to create a release branch.
To be fair this current patch release is quite large, in terms of number of fixes. Most of the time we only have 3-5 fixes per release, so it’s less of a chore. Also note that this cherry-picking approach is only done for patch releases. Minor (and major) releases are prepped by just branching of the master branch at the appropriate time.
If it can be done in a simpler way without too much effort I’m all for it though. Tagging commits and having a script (preferably a maven task) that automatically grabs those tags and merges into a release branch sounds fine. I’d like to see that it removes those tags after it’s done merging though, to avoid having lots of clutter.
Bumped to 2.2.1-SNAPSHOT, hudson failed, gave hudson a nudge and we'll see if it builds now or not.
Looks like it succeeded, good stuff.
I'll just leave #535 in there. Call it a freebee.
Jeen, you're in Australia right? Last I worked with someone in aussie land I ended up meeting during my morning, which would be your evening. Could manage something this week, unless you're still on vacation.
Yes, I’m in Melbourne (UTC+10). Thursday evening would be good for me. James? Where on the globe are you? Hope you're not on the west coast, cause trying to fit Europe, west coast and Australia in the same meeting is not the most comfortable to be honest.
James, would that work for you, this Thursday?
Jeen |