The doc issues have been resolved - I cleaned up some typos, etc that I found and tested the generated copy.
Moving onto 2.0 or 3.0, we should be able to bring this process into Confluence and rely on their exporting system, probably with scaffolding, etc... but for now, our little hack is doing the job nicely (I think). I would strongly encourage people to look at the new docs in 1.2. You can use the Guide to 1.2 Features page as a launching pad to find other new documentation. To me, a stable release candidate alone isn't a sufficient reason to release. We should also be sure the docs accurately reflect the new functionality :) Cris On 6/12/06, Gentry, Michael (Contractor) <[EMAIL PROTECTED]> wrote:
On the technical side, I think it is great that RC1 hasn't had a wealth of glitches reported. This speaks highly of all the hard work Andrus and others have done. On the more process-oriented side, the sooner we go "final" the sooner the cutover to the Apache namespace can be done and then release 2.0. This is something that needs to be done before trying to complete the incubation process. Obviously, this shouldn't drive the decision to make 1.2 final, but is something to keep in mind. Thanks everyone! /dev/mrg -----Original Message----- From: Kevin Menard [mailto:[EMAIL PROTECTED] Sent: Saturday, June 10, 2006 5:28 PM To: [email protected] Subject: Next Step? The first RC has been out for about a week and a half. Some minor issues seem to have come up on the users list, but nothing earth shattering that I can see. So, what's the end game here? Are we cutting an RC2 or just going with the final release? I'm not trying to be pushy, but I would like to avoid two months of RCs like Eclipse does ;-) -- Kevin
