I agree with Allen. For now, 1.3 should go out and get branched; we
should pull 2.0 back to the trunk and give it some chill/stabilization
time. I'm way behind even keeping up with 2.0 builds.
Also we probably ought to get through as many as possible of the
non-blocked items on the incubation checklist. (See STATUS.txt in the
top level of the SVN tree.) It would be really nice to have it down to
the license compatibility issues that have been escalated and nothing else.
--a.
Allen Gilliland wrote:
So, I agree that we've made great progess on 2.0, but I still think it's a
little ways away from a release.
I think Roller 1.3 should be released first and with a little lead time before
2.0 comes out. I think it's preferrable that users upgrade to 1.3 for a little
while before going to 2.0. If we can get 1.3 out this week then I would say
2.0 could be mid-October?
I also think that while the code base is feeling relatively stable now, we
should try and get as much UI testing in as possible. We've basically
completely rewritten the html and css for every page and we want to test that
as completely as possible accross different platforms and browsers.
#1 - I'm not sure if more work is going on with this, but I know we need to
sort out the 2.0 upgrade script with regards to this one. Right now the
upgrade script won't work on mysql InnoDB tables with all the dropping and
re-adding of foreign keys.
#2 - Indeed. This is tied to #1 as well. I sent out a bunch of sql last week,
but nobody had any comments. I don't want to put that sql in the upgrade
script if some of it is specific to mysql.
#3 - I would like to hold off on Acegi until I've had more time to try it out.
I haven't been able to try it since I've been focused on other 2.0 bug fixing.
#6 - Definitely.
#7 - I say we do this as soon as the 1.3 release is cut.
#9 - yah!
Also, we should try and figure out our strategy for upgrading current mysql
users from MyISAM to InnoDB. We've talked about this a little, but we need to
make some decisions.
-- Allen
On Mon, 2005-09-26 at 12:20, Dave Johnson wrote:
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
