Re: OpenJPA 2.0 milestone releases

[Craig L Russell]

Hi Jeremy,




Regards,

Craig

On Dec 4, 2008, at 8:11 AM, Jeremy Bauer wrote:

I don't understand why the version needs to be changed from simply 2.0.0-SNAPSHOT to 2.0.0-Mx-SNAPSHOT. Seems like we would be making trouble for folks who want to use the release. Wouldn't we want to make the change at the time we want to release, e.g. from 2.0.0- SNAPSHOT to 2.0.0-M2?

Three in favor, no oppose.  Motion passes.  :-)
The build artifacts for each milestone will be named
openjpa*-2.0.0-Mx-SNAPSHOT.jar, where x is the milestone number.  I'll
commit the pom updates for M1 shortly.

-Jeremy

On Wed, Dec 3, 2008 at 9:40 AM, Albert Lee <[EMAIL PROTECTED]> wrote:

+1.

Albert Lee.

On Wed, Dec 3, 2008 at 9:03 AM, Jeremy Bauer <[EMAIL PROTECTED]> wrote:

OpenJPA dev's,

into iteration 1, I think we should consider planning OpenJPA 2.0

Now that we have a few iteration periods defined and are getting content

milestone

releases. Based on a 3 (sometimes 4) week iteration schedule and the

fact

that it takes ~ a week to create and publish a release, how does a
milestone

release every other (ie. after each even numbered) iteration sound? If

we

discover that a milestone release every other iteration is not optimal,

we

can adjust as appropriate.

-Jeremy

--
Albert Lee.

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

smime.p7s
Description: S/MIME cryptographic signature