Because of ACCUMULO-2988 (upgrade path from 1.4.x --> 1.6.y, y >= 1), I'm hoping we can revisit this soon. Maybe get 1.5.2 out the door, followed by 1.6.1 right away.
-- Christopher L Tubbs II http://gravatar.com/ctubbsii On Fri, Jun 20, 2014 at 10:30 AM, Keith Turner <[email protected]> wrote: > On Thu, Jun 19, 2014 at 11:46 AM, Josh Elser <[email protected]> wrote: > > > I was thinking the same thing, but I also haven't made any strides > towards > > getting 1.5.2 closer to happening (as I said I'd try to do). > > > > I still lack "physical" resources to do the week-long testing as our > > guidelines currently force us to do. I still think this testing is > > excessive if we're actually releasing bug-fixes, but it does > differentiate > > us from other communities. > > > > I want to run some CI test because of the changes I made w/ walog. I can > run the test, but I would like to do that as late as possible. Just let > me know when you are thinking of cutting a release. > > Also, I would like to get 2827 in for the release. > > > > > > I'm really not sure how to approach this which is really why I've been > > stalling on it. > > > > > > On 6/19/14, 7:18 AM, Mike Drob wrote: > > > >> I'd like to see 1.5.2 released first, just in case there are issues we > >> discover during that process that need to be addressed. Also, I think it > >> would be useful to resolve the discussion surrounding upgrades[1] before > >> releasing. > >> > >> [1]: > >> http://mail-archives.apache.org/mod_mbox/accumulo-dev/ > >> 201406.mbox/%3CCAGHyZ6LFuwH%3DqGF9JYpitOY9yYDG- > >> sop9g6iq57VFPQRnzmyNQ%40mail.gmail.com%3E > >> > >> > >> On Thu, Jun 19, 2014 at 8:09 AM, Corey Nolet <[email protected]> wrote: > >> > >> I'd like to start getting a candidate together if there are no > >>> objections. > >>> > >>> It looks like we have 65 resolved tickets with a fix version of 1.6.1. > >>> > >>> > >> >
