+1 -- assuming the code is ready to go, I agree that it's a good idea to go straight to 1.0.
+1 as well to waiting until the TLP infrastructure is complete, which could take a week or more to unbrand from the Incubator, move the website content, etc. Eddie On 5/19/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
I personally lean towards just bumping it up to 1.0 and cutting a release as soon as possible after we complete the incubator->TLP process. A release number < 1.0 suggests to so many people that a product is not production-ready, and OpenJPA is so mature and in use in so many mission-critical systems that I think we should just bump all the open issues to a 1.0.1 or 1.1 release and get a 1.0 release out in the public. On May 19, 2007, at 4:31 PM, Craig L Russell wrote: > Hi, > > There's no urgency, but I think we should start discussing what our > first release should be out of incubation. > > Let's take a look at the issues in JIRA and decide if we think that > we're ready for a 1.0 release. If not, we can cut a 0.9.8 release > and make a list of 1.0 bugs/features to follow. > > Craig > > Craig Russell > Architect, Sun Java Enterprise System http://java.sun.com/products/jdo > 408 276-5638 mailto:[EMAIL PROTECTED] > P.S. A good JDO? O, Gasp! >
