I like releasing more often; the schedule looks good to me.
One suggestion: could we have a google calendar with the release
schedule? I can create it and add the committers as managers of the
calendar.
Thought: the release process is much better, especially for getting test
builds out. But the hoking and poking around on the server to sign,
copy files around, fix permissions, etc is still a drag. Would a shell
script help here?
I'm working on this wiki page
http://wiki.apache.org/portals/Pluto/CuttingRelease and I'd appreciate
feedback/updates on the page.
Looks good, the ball is rolling downhill!
David H. DeWolf wrote:
Now that 1.1.0 is out and we have a fairly automated release, I'd really
like to finally get a steady stream of releases out. We currently have
7 bug fixes that have been applied for the next release (1.1.1). I'm
fairly confident that those portals which rely on us will appreciate it
- especially as we get closer to really needing to ramp up on 286.
My goal is to finish up the remaining 2 fixes over the next week and
keep my eye open for additional bugs that come in. If that happens and
there aren't too many big issues, this is my idea for an upcoming
release schedule:
1.1.1:
- release weekend of march 3
- contains bug fixes for 1.1.0
1.1.2:
- release unknown
- branched from trunk after 1.1.1
- will continue bug fixes for 1.1.x line
1.2.0:
- release sometime in mid to late march
- becomes trunk after 1.1.1
- upgrade to java 1.5 requirement
- introduce generics, enhanced for each, etc. . .
Release early, release often :), let's try again. . .Thoughts?
David
