On Thu, Oct 10, 2013 at 9:00 AM, James Carman <ja...@carmanconsulting.com> wrote: > On Thu, Oct 10, 2013 at 8:35 AM, Gary Gregory <garydgreg...@gmail.com> 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 one. Gary > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
