On 5/20/07, Eddie O'Neil [EMAIL PROTECTED] wrote:
+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
that said, this is the OpenJPA project, and no matter what the state
of the infra move, anything that this group does now is independent
and disconnected from the incuabtor
On May 19, 2007, at 10:15 PM, Eddie O'Neil wrote:
+1 -- assuming the code is ready to go, I agree that it's a good
It sounds like there are a bunch of new things that we'll be doing in
this process; maybe we should do a 0.9.8 first to get the various
artifacts all sorted out, and then do a 1.0?
-Patrick
On 5/20/07, Geir Magnusson Jr. [EMAIL PROTECTED] wrote:
that said, this is the OpenJPA project, and no
The documentation probably needs some work. It doesnot look too friendly at
this moment for starters.
~dhrubo
On 5/20/07, Patrick Linskey [EMAIL PROTECTED] wrote:
It sounds like there are a bunch of new things that we'll be doing in
this process; maybe we should do a 0.9.8 first to get the
it's entirely up to you/us. this is a top level project and can
choose it's own way :)
geir
On May 20, 2007, at 1:25 PM, Patrick Linskey wrote:
It sounds like there are a bunch of new things that we'll be doing in
this process; maybe we should do a 0.9.8 first to get the various
artifacts
On May 20, 2007, at 10:25 AM, Patrick Linskey wrote:
It sounds like there are a bunch of new things that we'll be doing in
this process; maybe we should do a 0.9.8 first to get the various
artifacts all sorted out, and then do a 1.0?
I think that there will be enough confusion and retries to
I'll second two things that David mentioned:
1. Release 1.0 first. We have a release that as others have said,
passes the JSR 220 TCK and is production-ready. Let's make some
noise. Even though we won't have the incubator to officially bless
the releases, it will still take some time to
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
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
+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
10 matches
Mail list logo
