Hi Stack First I would like to thank you for the reviews and understand the decision. I would just like to highlight few facts if this does not make into 0.96 then we may have to -> Handle backward compatability issues with WAL. Currently inorder to retrieve tags we write a taglength thought it is 0. This would help us to replay WAL with Tags. -> Codecs like PRefixTreeCodec needs to be working for versions without Tags. Currently as PrefixTreeCodec is not out in any release these are not a problem for now.
So to avoid these problems we can get these Tags on 0.96 release. May be a few more days of time. Is it possible? I can try getting people for more reviews too. Thanks Stack. Nice of you. Regards Ram On Thu, Aug 15, 2013 at 7:09 AM, Devaraj Das <d...@hortonworks.com> wrote: > A late breaking one- https://issues.apache.org/jira/browse/HBASE-9227. > Kindly consider for the upcoming RC. > > > On Wed, Aug 14, 2013 at 1:26 PM, Andrew Purtell <apurt...@apache.org> > wrote: > > > On Wed, Aug 14, 2013 at 12:57 PM, Stack <st...@duboce.net> wrote: > > > > > I see no reason that 0.98 cannot come out a week or a month after 0.96; > > > > tags is close and justification enough for a major release. > > > I propose Andrew as RM for 0.98/1.0.0 if he is up for taking it on. > > > > > > I would be pleased to volunteer to RM 0.98. > > > > It will be a challenge for anyone to live up to your outstanding example > > for 0.96. > > > > If I were to be your RM for 0.98, then I would suggest a .0 release in > the > > beginning of October. There are 42 open issues against 0.98 specifically > > and I would like to also provide everyone some time for post 0.96 release > > thinking. > > > > I am not sure we should move from 0.98 to 1.0 without another interim > > release, that would be a call for a later time perhaps, maybe a 1.0 > release > > at the start of January 2014. > > > > > > -- > > Best regards, > > > > - Andy > > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > > (via Tom White) > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
