Hey Henry,
Thanks. I'm helping to speed up the VOTE via the cross post. In doing so, we
don't need to wait an additional 72 hours now, if we get 3 IPMC +1s (even if
it's just Gora mentors who are on the IPMC)...
Cheers,
Chris
On Mar 10, 2011, at 10:13 PM, Henry Saputra wrote:
> Hi Chris,
>
>
Hi Chris,
Thanks for the crosspost rc3 announcement to @general list.
I didnt do cross post because I thought 72 hours has not passed since
I announced it to @general.
- Henry
On Wed, Mar 9, 2011 at 7:02 PM, Mattmann, Chris A (388J)
wrote:
>>
>> I guess we dont need to VOTE again within Gora co
>
> I guess we dont need to VOTE again within Gora community, right?
Unfortunately, we do :(
But what I'd do is just cross-post the VOTE to gora-dev@incubator.a.o and
general@incubator.a.o, indicating this is RC #3, and what has been addressed.
Keep up the good work Henry!
Cheers,
Chris
>
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 wrote:
> On 3/9/11 10:11 PM, Andrzej Bialecki wrote:
>>
>> On 3/9/11 9:32 PM, Henry S
Thanks guys for working this.
Thanks Andrzej, and thanks Henry!
Cheers,
Chris
P.S. BTW, Sebb's comments should be addressed, and glad that Andrzej did. This
is why the incubator review on general@incubator.a.o is important even after
our 3 +1s on gora-dev...
On Mar 9, 2011, at 12:32 PM, Henry
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
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 tru
Since Andrzej already check in to trunk, any changes for 0.1 release
need to be double fixed in both trunk and branch, right?
I dont want to merge trunk to branch with new changes for next release.
Also I have sent email to @general list and got some feedbacks about
our release. Maybe Andrzej or C
On 3/9/11 8:53 PM, Julien Nioche wrote:
Meaning that we need to do a new RC with the recent changes from Anrdzej and
go through the voting again?
I'd rather we pushed 0.1 out as it was on the latest RC you did and mark the
trunk as 0.2 now. Or did I misinterpret your comment?
That was my point
> I think we are good now. Any fix for 0.1-incubating should be
> happening in the branch.
>
> - Henry
>
> On Wed, Mar 9, 2011 at 10:28 AM, Andrzej Bialecki wrote:
> > Hi,
> >
> > Can we update the version on trunk to something else than 0.1-incubating?
>
I think we are good now. Any fix for 0.1-incubating should be
happening in the branch.
- Henry
On Wed, Mar 9, 2011 at 10:28 AM, Andrzej Bialecki wrote:
> Hi,
>
> Can we update the version on trunk to something else than 0.1-incubating?
> e.g. 0.2-incubating ;)
>
> --
> Be
Hi,
Can we update the version on trunk to something else than
0.1-incubating? e.g. 0.2-incubating ;)
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || |
12 matches
Mail list logo
