Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD3E5F322 for ; Thu, 4 Apr 2013 17:41:17 +0000 (UTC) Received: (qmail 96635 invoked by uid 500); 4 Apr 2013 17:40:32 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 95946 invoked by uid 500); 4 Apr 2013 17:40:31 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 82931 invoked by uid 99); 4 Apr 2013 17:33:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Apr 2013 17:33:36 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [98.139.213.164] (HELO nm14-vm0.bullet.mail.bf1.yahoo.com) (98.139.213.164) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 04 Apr 2013 17:33:24 +0000 Received: from [98.139.214.32] by nm14.bullet.mail.bf1.yahoo.com with NNFMP; 04 Apr 2013 17:33:03 -0000 Received: from [98.139.212.193] by tm15.bullet.mail.bf1.yahoo.com with NNFMP; 04 Apr 2013 17:33:03 -0000 Received: from [127.0.0.1] by omp1002.mail.bf1.yahoo.com with NNFMP; 04 Apr 2013 17:33:03 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 771639.5308.bm@omp1002.mail.bf1.yahoo.com Received: (qmail 80075 invoked by uid 60001); 4 Apr 2013 17:33:03 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1365096783; bh=VWhGCH2v289773LRp6l86mxwhYaGhhJVr3hwOITOWIM=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=QJa7m2Xtcb+8eQGeKGRTJXigOQo2KKwpJZkSQF15MjbeuYT6pHAgmgynnVGmtrugExlpGqaktAqc9TJ1ICWJahsMUph81arET4OU1+URenASSPBOswjTIAsEv+ewAOTuyQ92/0wGnIWLRSdhFg4+e1VyeDlJ1SxUY0CuNclK7Tg= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=SsqQw6z3NTQPmGYUNAc2+/31uwmNLqqUDsHMlGs+QrAdJ0ce7lTcZ0IMhnSVQGWy4f3dYUOo/YkmJkVCQeDV0dkgHt6q60RF8PWP1YbtBAS5DK5+Cz1zttIwpW1bFq2tZNh5VqV+GWYQ52sOL+Dtnyl2hKXuqAcP6PrKc+vJPAU=; X-YMail-OSG: QjSBTfAVM1mdGPOuzqzNrZ5SxcQvtSF_u7FrfXuFSyUi2fV hG.d5sPCaIGqowx8aqDFZXFwMW9PszO1BjexJifS3YqRVqoqBaKuEXel70OK vv6cDZmo74IVMRNmsB6iRtOgHGUC5XENey8mIlpwS0fInX8fL1AaKuQoSqJL QBk1CURLLjEQYE.ftSajm9C9PTmqbBNYIhJ0MLtlSyQGjg.1zIwY4O4ojSYg Ua8Iy_QQUHeSOosYpXtQG0r4wy22BPld0V.TsGUkruQPMsb1awujScXp9fjc 7lNEEa4IXMHBhHwjNBYcUbwKfAVMbBVCnf60WCyWuv_mnGltl1C6yg.yVy96 zTp07goXulK4fAQrERrQYnjgMZVkMsOF3piX55uvOKPmm6rvaO2p3T3XJAue fz347QZvQ18GnbSaRLVQPrg4v.LJL3tTUsi4C3RZQDQMGRIHrkXZgopdsTRD Lo59keea.znGB_J96WeEhrdaUlwy4HzB.E1okwREoDudiGg5XLkpMC848p1x 3sEH.Q5B_Oj4v5ea3VLs- Received: from [24.130.114.129] by web140603.mail.bf1.yahoo.com via HTTP; Thu, 04 Apr 2013 10:33:03 PDT X-Rocket-MIMEInfo: 002.001,WWVzLCBJIHRoaW5rIHdlIHNob3VsZCByZW1vdmUgdGhlIDAuOTYgdGFnLiBTdGFjayBzYWlkIHRoZSBvdGhlciBkYXkgdGhhdCBoZSBzaG91bGQgaGF2ZSBqdXN0IHJlbmFtZWQgMC45NiB0byAwLjk1IHJhdGhlciB0aGFuIG1vdmluZyBhbGwgdGhlIGlzc3Vlcy4KClRoZSByZXN0IGlzIGFscmVhZHkgd2hhdCBJIGhhdmUgYmVlbiBkb2luZyBmb3IgaXNzdWVzIEkgYW0gY29tbWl0dGluZyAoc28gKzEgOikgKSwgYnV0IEkgZGlkIG5vdGljZSB0aGF0IG5vdCBhbGwgaXNzdWVzIGFyZSB0YWdnZWQgY29ycmVjdGwBMAEBAQE- X-RocketYMMF: lhofhansl X-Mailer: YahooMailWebService/0.8.140.532 References: <1365095403.68604.YahooMailNeo@web140604.mail.bf1.yahoo.com> Message-ID: <1365096783.48709.YahooMailNeo@web140603.mail.bf1.yahoo.com> Date: Thu, 4 Apr 2013 10:33:03 -0700 (PDT) From: lars hofhansl Reply-To: lars hofhansl Subject: Re: Marking fix version To: "dev@hbase.apache.org" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="-1172831624-1771001352-1365096783=:48709" X-Virus-Checked: Checked by ClamAV on apache.org ---1172831624-1771001352-1365096783=:48709 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Yes, I think we should remove the 0.96 tag. Stack said the other day that h= e should have just renamed 0.96 to 0.95 rather than moving all the issues.= =0A=0AThe rest is already what I have been doing for issues I am committing= (so +1 :) ), but I did notice that not all issues are tagged correctly.=0A= =0A=0A-- Lars=0A=0A=0A=0A________________________________=0A From: Jonathan= Hsieh =0ATo: dev@hbase.apache.org; lars hofhansl =0ASent: Thursday, April 4, 2013 10:15 AM=0ASubject: Re: Markin= g fix version=0A =0A=0AThe argument for excluding the 0.96 tag makes sense.= =A0Can we agree to do this:=0A=0A=0ACommit only to trunk: Mark with 0.98= =0ACommit to 0.95 and trunk : Mark with 0.98, and 0.95.x=0ACommit to 0.94.x= and 0.95, and trunk:=A0Mark with 0.98, 0.95.x, and 0.94.x=0A=0ACommit to 8= 9-fb: Mark with 89-fb.=0ACommit site fixes: no version=0A=0AShould we remov= e 0.96 tag for now until the branch appears again?=0A=0AThanks,=0AJon.=0A= =0AOn Thu, Apr 4, 2013 at 10:10 AM, lars hofhansl wrote:= =0A=0AThank Jon,=0A>=0A>I do not think we have to include anticipated futur= e branches in the tags.=0A>The release notes are not accumulative but list = changes made for each release.=0A>=0A>So if something is in 0.95.x a 0.96 t= ag neither needed nor wanted (IMHO) until we actually have a *parallel* 0.9= 6 branch.=0A>=0A>That is why all 0.95+trunk changes *have* to be tagged wit= h 0.98 as well, because at this point the two branches are in parallel. Act= ually we should go through and make that so in jira.=0A>=0A>That means the = 0.96 tag is not needed right now (and in fact will make just confusing, bec= ause at the time we do release 0.96 we'll see the same issue in the release= notes twice)=0A>=0A>-- Lars=0A>=0A>=0A>=0A>_______________________________= _=0A>=A0From: Jonathan Hsieh =0A>To: dev@hbase.apache.org= =0A>Sent: Thursday, April 4, 2013 8:40 AM=0A>Subject: Marking fix version= =0A>=0A>=0A>Hey all,=0A>=0A>I just wanted to make sure we are on the same p= age here when we committing=0A>code and that we are consistent when marking= fix version in the jira.=A0 Its=0A>pretty important that we get this right= because our release notes are=0A>generated from these as of 0.94.=0A>=0A>H= ere's what I'm doing and suggesting=0A>=0A>Commit only to trunk: Mark with = 0.98=0A>Commit to 0.95 and trunk : Mark with 0.98, 0.96, and 0.95.x=0A>Comm= it to 0.94.x and 0.95, and trunk: Mark with 0.98, 0.96, 0.95.x, and=0A>0.94= .x=0A>Commit to 89-fb: Mark with 89-fb.=0A>Commit site fixes: no version=0A= >=0A>My understanding is that 0.96 will be a branch off of 0.95 -- so any f= ix to=0A>0.95 is a fix to 0.96 until 0.96 branches.=0A>=0A>Thanks,=0A>Jon.= =0A>=0A>--=0A>// Jonathan Hsieh (shay)=0A>// Software Engineer, Cloudera=0A= >// jon@cloudera.com=0A=0A=0A-- =0A// Jonathan Hsieh (shay)=0A// Software E= ngineer, Cloudera=0A=0A// jon@cloudera.com ---1172831624-1771001352-1365096783=:48709--