Allen and I have been testing and fixing bugs in Roller 2.0 for the
past week and the code-base is looking pretty good. I think we have all
the features that we need for our next production deployments and the
bug list is dwindling.
So, my question is, how do we wrap up the official un-official Roller
2.0 (incubating) release?
There are still a number of open issues:
1 - Is the Derby/DB2 stuff in place or is work still outstanding?
2 - Need to get database upgrade script are ready (Allen has a faster
upgrade script)
3 - Acegi security: should we try to get this in for Roller 2.0, or
save it for later?
4 - Need to finish new User Guide
5 - Need to start new Install Guide
6 - Need to prepare Roller 1.3 release (for those too timid to try 2.0)
7 - Need to move trunk to roller_1.3 branch and roller_2.0 branch to
the trunk
8 - Vote on the Roller 2.0 release
9 - Establish a web page at apache.org
Comments on those issues?
Any other issues to take in to account for 2.0? Any other patches we
should consider?
- Dave
