Sounds like a plan. Let's do it. On Mon, Aug 29, 2011 at 10:36 PM, Martijn Dashorst <[email protected]> wrote: > All, > > As we approach the end of summer (whatever you can call this travesty > called june, july and august) we also approach a milestone in our > development: the end of our development cycle for Wicket 1.5. > > As far as I can tell, 1.5 has reached a point that it is ready to be > released to our general user community. 1.5-rc7 hasn't shown any major > problems for the core team's projects, and can be promoted to our > general release (in my opinion). > > But before we start waving the flag and holding a ticker tape parade, > I would like to do the following: > > - review the README.txt as it contains outdated information > - review the release notes, merge them together? > - review the migration guide, make it very easy to find in the wiki > - write up a good release announcement with the major benefits for > this release noted > - updates to the README and release notes will trigger a new package, > so we might > need to re-build and re-vote > > I had hopes to provide is with a new website design, but the proposed > solution is quite hard to implement, and I guess it will be difficult > to maintain. So I'm opting for a simpler design, but will have to work > on that. > > Next we will need to release a 1.5.1 and 1.5.2 etc. I imagine we > should build a 1.5.1 after 3 weeks. I can also imagine a 1.5.2 3 weeks > after that. At that time we should branch 1.5, EOL 1.4 and start work > on the next wicket version. If nothing bad is found in 1.5.0 and we > can release 1.5.1 with few issues, I propose branching and EOL-ing 1.4 > at that moment. > > As for a timeline: I understand that tuesdays are the best day of the > week to release software and announcements. As we need to flesh out > the details, we have about a week for that (including votes and > discussing this playbook). > > I propose we fix our release documentation in the coming days, ship > 1.5.0 on tuesday 6 september and do a 3 weekly bug fix release until > 1.5.2. Depending on the number of issues found and their severity of > course. I suggest starting work on the next Wicket version when 1.5.x > bug fixing takes less of our time. > > What do you guys think? > > Martijn >
-- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
