On Mon, Jun 5, 2017 at 9:17 AM, Jochen Wiedmann <jochen.wiedm...@gmail.com> wrote:
> On Mon, Jun 5, 2017 at 5:20 PM, sebb <seb...@gmail.com> wrote: > > >> I'd like us to be able to push out a new release with minimal changes > >> at any given time. If we have, for example, 1.6 as the target, and the > >> previous > >> release had 1.5 as the target, then we'd loose that ability, IMO. > >> (Think security releases.We've had quite a few in the past.) > > > > Understood, but I'm not sure why you feel the lack of a 1.6 release > > would prevent a security release. > > Surely we could just apply the fixes to the previously released code > > and change to 1.6 at the same time? > > Because the result clearly be binary incompatible to its predecessor, > and that's the whole point of such an emergency release. We'd want a > drop-in replacement. > If someone wants a fix for something that runs on 1.5, they are welcome to provide a PR. I do not think we need to handcuff ourselves to Java 5. If your runtime is stuck on Java 5, your likely to have other more pressing security issues to address... Gary > > Jochen > > > -- > The next time you hear: "Don't reinvent the wheel!" > > http://www.keystonedevelopment.co.uk/wp-content/uploads/2014/10/ > evolution-of-the-wheel-300x85.jpg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
