If we could manage it this way, that'd be great, Lars. If you're up for being the RM for 4.9, that'd be much appreciated. Thanks, James
On Saturday, July 2, 2016, <[email protected]> wrote: > Hi all, > > This reminds me a bit of the HBase times before we went to a more or less > strict monthly release train. > It was harder to stabilize a release and there were lots of last minutes > changes and fixes, just because each release was big (in terms of the > number of changes).In addition folks were worried when the next release > would come about and would push many changes towards the end of the release > cycle. > > Most of that stopped with the monthly releases. Commit rates are more > even, there's no last minute flurry of changes (after all, the next release > is just a month away).Users get more frequent release, each with less > change and less risk, and they get bug fixes earlier. > > 4.7 was about 4 months ago, 4.6 was about 4 months before that.For my > (personal) taste that is fairly infrequent and the release are too big and > too hard to stabilize - again just my personal opinion, please do not take > this in a negative way. > > Any interest in going to smaller and more frequent releases in Phoenix? > Thoughts? Comments? > > Thanks. > -- Lars > > (If it helps I'll offer to RM a few releases. In that case I'd adhere to a > monthly release train; whatever change or feature is ready gets on the > train, what's not ready waits for the next train to arrive a month later.) > From: James Taylor <[email protected] <javascript:;>> > To: "[email protected] <javascript:;>" <[email protected] > <javascript:;>>; Ankit Singhal <[email protected] <javascript:;>>; Samarth > Jain <[email protected] <javascript:;>>; Rajeshbabu > Chintaguntla <[email protected] <javascript:;>>; Thomas > D'Silva <[email protected] <javascript:;>>; Mujtaba Chohan < > [email protected] <javascript:;>> > Sent: Friday, July 1, 2016 2:02 PM > Subject: Re: where are we at with the RC? > > How we looking for the RC? > > On Friday, July 1, 2016, Samarth Jain <[email protected] > <javascript:;>> wrote: > > > PHOENIX-2724 has a workaround in PHOENIX-3040 that I have checked in. I > > think we can fix PHOENIX-2724 in a patch release, if needed. > > > > The remaining outstanding JIRAs that I know of are: > > https://issues.apache.org/jira/browse/PHOENIX-2902 > > https://issues.apache.org/jira/browse/PHOENIX-29 > > <https://issues.apache.org/jira/browse/PHOENIX-2902>99 > > > > > > > > On Thu, Jun 30, 2016 at 9:48 PM, <[email protected] <javascript:;> > <javascript:;>> wrote: > > > > > PHOENIX-3037 (Andy just committed) needs to get in. > > > -- Lars > > > From: Samarth Jain <[email protected] <javascript:;> > <javascript:;>> > > > To: dev <[email protected] <javascript:;> <javascript:;>> > > > Cc: Ankit Singhal <[email protected] <javascript:;> <javascript:;>> > > > Sent: Tuesday, June 28, 2016 9:58 AM > > > Subject: Re: where are we at with the RC? > > > > > > PHOENIX-3028 is in. PHOENIX-2724 is a blocker as of now. Will work on > > this > > > today to see if it is just a matter of tuning phoenix config or > something > > > more. > > > If time permits, I would like to opportunistically get PHOENIX-3035 in. > > > > > > On Mon, Jun 27, 2016 at 10:56 PM, James Taylor <[email protected] > <javascript:;> > > <javascript:;>> > > > wrote: > > > > > > > What are the outstanding JIRAs? Would it be possible to update this > > daily > > > > so we can zero in on getting an RC up? If folks could commit there > > > > outstanding patches (or find a committer to do it for you), that be > > much > > > > appreciated. > > > > > > > > Thanks, > > > > James > > > > > > > > > > > > > > > > > > > > >
