Great - please consider going through the JIRAs marked for 0.15.0 and set the fix version to 1.0.0 with some commentary as to why it should be included and preferably with some assessment of perceived risk to destabilizing what is essentially the 0.14.0 release.
We can then circle back on those and continue discussion on the JIRAs themselves - if need be. On Mon, Dec 18, 2017 at 9:38 AM, Colm O hEigeartaigh <cohei...@apache.org> wrote: > +1. > > Colm. > > On Mon, Dec 18, 2017 at 2:34 PM, Philip Zampino <pzamp...@gmail.com> > wrote: > > > Sounds good. I've already implemented a few patches I would like to see > in > > 1.0.0, and I agree that we should go through the others +1 > > > > On Mon, Dec 18, 2017 at 9:12 AM, larry mccay <lmc...@apache.org> wrote: > > > > > All - > > > > > > As we discussed back in November [1], we should follow up the recent > > 0.14.0 > > > release with a 1.0.0 with the renaming of the class packages. > > > > > > In addition to the package renames, we could also accommodate any fixes > > or > > > upgrades that would be work well toward the backward compatibility > > > commitments that a 1.0.0 release implies and/or any security related > > fixes. > > > > > > I don't anticipate more than a handful of JIRAs to be attached to this > > > release. > > > > > > My proposal would be that we go through the rather large set of 0.15.0 > > fix > > > version JIRAs and determine those few that absolutely need to go into > > 1.0.0 > > > and defer the rest to 1.1.0. > > > > > > Given the holidays on the horizon, we may want to target a release date > > of > > > Friday 1/12 or earlier. If we keep the scope extremely tight, we can > > > probably get it out earlier. > > > > > > thoughts? > > > > > > --larry > > > > > > 1. > > > http://mail-archives.apache.org/mod_mbox/knox-dev/201711. > > > mbox/%3CCACRbFyjvzAzQ%3DA-JfxYVhAD4DhABeNRBbhLPs4dPTPTtC > > > 1BMNg%40mail.gmail.com%3E > > > > > > > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com >
