On 1/19/06, David M Johnson <[EMAIL PROTECTED]> wrote: > Allen and I are planning to deploy Roller 2.1 to production sites > next week, so we're going into code freeze mode today. At the same > time, I'd like to try to get an "Apache Roller (incubating)" release > out. > > I propose this plan: > > 1 - Write a what's new in Roller 2.1 page for the wiki > 2 - Create Roller 2.1 release candidate (today or tomorrow) > 3 - Testing through Thursday of next week > 4 - Fix or defer remaining issues here: http://tinyurl.com/d3cwa
Why not doing this before hand 1? ie) Why are we preparing to release 2.1 when it's only 60% complete? Are the other 40% less essential for Sun Roller? Do those priorities fit with other users (Elias/Matt)? > 5 - Call for release vote late next week 5.5 - notify [EMAIL PROTECTED] > 6 - Profit! 7 - IRS inspection of non-profit organization suddenly making profits. > I'll do 1, 2 and 5. I need help with 3 and 4. Thanks for volunteering :) +1 from me. I'm definitely available to test a postgres update + install. Hopefully a derby one too on the version I setup on my laptop. Hen
