On Mon, Mar 6, 2017 at 3:21 PM Timothy Bish <[email protected]> wrote:
> On 03/06/2017 03:02 PM, Clebert Suconic wrote: > > Does he need a 1.5.4? or a 2.0.0 would work? > > > > With the refactoring I just finished I think a 2.0 is eminent to go > > out soon. I had proposed the refactoring I just finished and I had > > held 2.0 before for it.. so I think it's ready to go now. > > > > > > I think the next to be released would be 2.0... > > Projects like Camel do multiple releases without issue. Asking someone > to jump from 1.5.x to 2.0.x is a major version bump with significant > risk, so providing a bug fix release is a nice thing to do for the > community. If someone offers to run a release I wouldn't discourage > them from doing so. > > Big +1 Even if we have a 2.0 coming soon, maintaining old versions should be easy enough to help those that may need it. So far it sounds like there would be no objections to cutting the current 1.x branch as a 1.5.4, so I can plan to start that process tomorrow evening. > > Unless it wouldn't be too overwhelming to release both 1.5.4 and 2.0.0 > > at the same time. > > > > On Mon, Mar 6, 2017 at 12:27 PM, John D. Ament <[email protected]> > wrote: > >> Hey guys > >> > >> Just wondering, is there a plan right now for a 1.5.4? Romain's > blocked a > >> bit on the issue he reported this morning (morning my time at least) so > I > >> wanted to get him something to help fix it this week if possible. > >> > >> If there is no plan, I can execute the release steps to prep a release > and > >> call a vote. Thoughts? > >> > >> John > > > > > > > -- > Tim Bish > twitter: @tabish121 > blog: http://timbish.blogspot.com/ > >
