commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [JCS] missing 2.2 release in jira?
Date Tue, 05 Sep 2017 18:27:55 GMT
On Sun, Sep 3, 2017 at 11:42 PM, Romain Manni-Bucau <rmannibucau@gmail.com>
wrote:

> Hmm 2 questions just to ensure we are aligned and mail didn't loose
> information:
>
> - for trunk: do we move the version to 2.3-SNAPSHOT?
>

If you expect the next version to include _minor_ changes (like minor new
features), then 2.3-SNAPSHOT is fine. If you are only going to fix bugs,
then 2.3.1-SNAPSHOT would be appropriate.


> - for next release: i'm not sure what's the difference is at the moment but
> any reason to not do a 2.3 from trunk? (asking from the jcache perspective
> i upgraded to the "snapshot" without issues)
>

Seems OK to me.

Gary


>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2017-09-03 22:19 GMT+02:00 Thomas Vandahl <tv@apache.org>:
>
> > On 03.09.17 20:17, Romain Manni-Bucau wrote:
> > > Thanks Thomas
> > >
> > > Is it the same for the code? Just realised pom were not up to date too.
> >
> > I released from a branch as some braking changes are already checked in
> > into trunk. I'd kindly ask you to do the same if you are planning for a
> > bugfix release.
> >
> > Bye, Thomas.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message