This vote is now cancelled. I agree. We need to understand/document/fix class loading issues and the version string. I've a patch for the latter but I think the former will take a little longer.
It was good to attempt a 6.0 release but I don't think we should keep the code freeze going any longer so I suggest we attempt 6.0M1 when we produce 5.0M12. So consider the full code base re-opened for commits. Regards, Mark. In message <4a9f7248.4070...@gmail.com>, Tim Ellison writes: > > I vote -1 because it is unclear to me what the limitations are on > loading some class files, and would like that fixed (if seriously > limiting) or mentioned in the readme (if acceptable as a known issue). > > I also think that HARMONY-6330 should be fixed before declaring 6.0M1. > > (There may be others as I didn't get too far through my testing regime) > > Regards, > Tim > > On 01/Sep/2009 08:30, Mark Hindess wrote: > > There was some agreement that we should create a 6.0 milestone so I'm > > going to begin a vote. If anyone feels that three days isn't enough > > time to complete testing then please just ask for more time. > > > > I have created a signed source archive for this revision and made it > > available at: > > > > http://people.apache.org/~hindessm/6.0m1/ > > > > Please test these artifacts and then vote for declaring these source > > archives as 6.0 milestone 1, and opening up the remaining frozen code > > trees for general development once again. > > > > This vote will be open for at least 3 days, or until all binding votes > > have been cast (if earlier). > > > > If the vote is successful, binary builds from that level will be made > > available on the download page. > > > > Regards, > > Mark.
