Mailing-List: contact gora-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: gora-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of henry.saputra@gmail.com
 designates 209.85.214.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=VU/C7cuOI90xqzlBqlWNgzY+Rzm0B81hR+9QeE27kREnwhyomSQQF1lh52FD2iqkuo
         FHDduq9WJns9rFRKX/qpkL1cWHAYaUgd2nLvpw+fGoMaSKYM8sdLoJ3xSHYcMfZkAYpV
         4pcH5AuREWyFLqKEpJv2LbL6runAt8+iCRQBE=
MIME-Version: 1.0
In-Reply-To: <4D7801D7.80507@getopt.org>
References: <4D77C6B9.4090909@getopt.org>
	<AANLkTik+FgjFi7+ui0urgOwGhcsCbAqJDWbfx8kE0qqT@mail.gmail.com>
	<AANLkTik3n10E69HJkiJvaqwqYA0YP-F=yQ2H99pn-UUV@mail.gmail.com>
	<4D77E2D5.1010904@getopt.org>
	<AANLkTi=LiqW3Ph3z-nmoaCZvK=3ffzEbYT5Fg5OvMiJu@mail.gmail.com>
	<4D77ECE9.7050704@getopt.org>
	<4D7801D7.80507@getopt.org>
Date: Wed, 9 Mar 2011 18:56:48 -0800
Message-ID: <AANLkTimMdmh6ysHZCTFZqHfW3idaS58xmDJLMKM0J+Uj@mail.gmail.com>
Subject: Re: Version on trunk
From: Henry Saputra <henry.saputra@gmail.com>
To: gora-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks Andrzej. I saw the checkins to 0.1-incubating branch and will
create new rc tag.

I guess we dont need to VOTE again within Gora community, right?

- Henry

On Wed, Mar 9, 2011 at 2:40 PM, Andrzej Bialecki <ab@getopt.org> wrote:
> On 3/9/11 10:11 PM, Andrzej Bialecki wrote:
>>
>> On 3/9/11 9:32 PM, Henry Saputra wrote:
>>>
>>> Since Andrzej already check in to trunk, any changes for 0.1 release
>>> need to be double fixed in both trunk and branch, right?
>>
>> Yes. My check-in to trunk is not relevant - the next RC should be done
>> from branches/0.1-incubating.
>>
>>> I dont want to merge trunk to branch with new changes for next release.
>>
>> If we can avoid it - sure. But occasionally this happens and it's not a
>> big deal to do so.
>>
>>>
>>> Also I have sent email to @general list and got some feedbacks about
>>> our release. Maybe Andrzej or Chris could help response to the
>>> comment?
>>
>> I need to subscribe first .. ;) I looked at the archive, and indeed we
>> need to fix these issues.
>>
>> In any case, as I wrote above, the standard procedure is that the next
>> RC should be created from branch 0.1 - if you guys can add the missing
>> NOTICE and DISCLAIMER there and fix the headers I will gladly port these
>> changes back to trunk.
>
> I found myself with a few minutes to spare, so I started fixing this, it
> should be ready in a moment. I'll apply the change on
> branches/0.1-incubating, and the next RC should be generated from this.
>
>
> --
> Best regards,
> Andrzej Bialecki =C2=A0 =C2=A0 <><
> =C2=A0___. ___ ___ ___ _ _ =C2=A0 __________________________________
> [__ || __|__/|__||\/| =C2=A0Information Retrieval, Semantic Web
> ___|||__|| =C2=A0\| =C2=A0|| =C2=A0| =C2=A0Embedded Unix, System Integrat=
ion
> http://www.sigram.com =C2=A0Contact: info at sigram dot com
>
>


--=20
Thanks,
Henry