commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <>
Subject Re: [DISCUSS] Allow unstable 0.x OR -Milestone releases [Was: [DISCUSS] Putting several unmaintained components to dormant]
Date Thu, 10 Oct 2013 13:49:03 GMT
On Thu, Oct 10, 2013 at 9:00 AM, James Carman
<> wrote:
> On Thu, Oct 10, 2013 at 8:35 AM, Gary Gregory <> wrote:
>> I think "milestone" releases works if you have a clear development
>> plan and schedule. I've never seen it be the case in Commons. Calling
>> "releases" to Maven and dist, Alphas and Betas make more sense for us
>> IMO.
> I don't care what we call it.  They key is that we set up the
> expectation with our users.  If you use this release, do NOT use it in
> production code.  It is not "supported", meaning we aren't going to
> fix bugs in that alpha version if we have already released its
> subsequent full release version (or a subsequent alpha).

Of course, but naming is important, it communicates intent. With alpha
and beta, you can describe two kinds of releases, with milestone, only


> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

E-Mail: |
Java Persistence with Hibernate, Second Edition
JUnit in Action, Second Edition
Spring Batch in Action

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message