Thanks, Ankit. How likely is it that PHOENIX-3111 will happen? Since it's not a regression and this is the first we've heard of it, maybe not very likely? Or is it more common with the new local index implementation? If it's a matter of a few days, probably worth holding off on the RC.
Thoughts? On Mon, Jul 25, 2016 at 8:28 AM, Ankit Singhal <[email protected]> wrote: > Moving PHOENIX-3111 to 4.8.1 as per discussion with Rajeshbabu. Let me know > if someone thinks it's important for 4.8.0. > Now currently, the only outstanding blocker for 4.8.0 is PHOENIX-3113 and > which has a simple fix. So, by tomorrow morning IST, we should have RC1 > out. > > Regards, > Ankit Singhal > > > > On Mon, Jul 25, 2016 at 10:16 AM, James Taylor <[email protected]> > wrote: > > > Can we get an RC up today, please? There's one JIRA waiting to be > committed > > and I think we're good after that. All licensing issues have been fixed. > > Thanks, > > James > > > > On Sunday, July 24, 2016, <[email protected]> wrote: > > > > > Also, can we branch 4.8-x in git?That way bigger changes can still go > > into > > > the 4.x branches, while bugs are fixed in 4.8-x branches. > > > -- Lars > > > > > > From: James Taylor <[email protected] <javascript:;>> > > > To: "[email protected] <javascript:;>" <[email protected] > > > <javascript:;>> > > > Sent: Thursday, July 21, 2016 7:16 PM > > > Subject: new 4.8.0 RC? > > > > > > How about a cutting a new RC now that the licensing work is complete, > > > Ankit? Looks like we can simplify the voting too by just having a > single > > > vote across all versions by just include all the information in one > VOTE > > > thread. > > > > > > Would be good to get PHOENIX-3078 in too, if possible. We've had a few > > > other fixes come in which IMHO are all ok to include in the new RC. > > > > > > Thanks, > > > James > > > > > > > > > > > >
