Hi Claudio and everyone,
OK, I just woke up. This is so much harder thanks to my inconvenient
timezone :-)
I didn't mean to stress you out, I'm sorry that I have. But I guess
I've missed your deadline which means no release thanks to my bad
timing (in several ways). I wanted to start planning this tutorial
earlier, and I knew that it would result in some API changes, but I
was so busy with organising PyCon AU that I just couldn't find the
time.
I could do the release, but I'd really rather not since Claudio has
done such a fine job to now. I guess that leaves me no choice but to
revert the changes I've made, which I'll do now.
Richard
On Thu, Jul 8, 2010 at 7:51 AM, claudio canepa <[email protected]> wrote:
>
> On 7 jul, 09:10, claudio canepa <[email protected]> wrote:
>> Ways out:
>>
>> - Some other committer is willing to tell 'I know how the others init
>> work,
>> and there will be no problem with the news init' . You say: 'all the test
>> runs'. All right , in that scenario I will trust both, pack what it is in
>> trunk and release today.
>>
>> - I realize the first is hard due to time frame. It may be someone is
>> willing to review, but need more time.
>> Fair, but probably nobody wants to wait five weeks, and I won't have any
>> motivation to return to this point in five weeks. So I don't do the
>> release,
>> Cocos nominates another person to make it happen, and hopefully in some
>> days
>> it can be out. Really at this point building package and documentation is
>> easy, basically all in the release chain is updated and tested. We have a
>> release, only that other person releases.
>>
>> - We settle for not introduce the features in discussion. No init for
>> Layer
>> and Scene. I release today.
>>
>> How is the decision taken ?
>> option 3 is Richard decision
>> option 1 is any committer decision
>> option 2 I think its for the Cocos historical leaders, Lucio or Riq.
>>
>> I will be perfectly well with any decision, really.
>>
>> To close, I will be out now , 9:00 local, return home between 16:00 and
>> 17:00, can work from there to max 2:00
>> I will be offline till 17, and will be no time for so much discussion
>> after.
>> If there is an explicit decision by the time, much better.
>>
>> cheers
>>
>> --
>> claudio
>
> Ok, now it is 18:40, nothing new.
> I choose 2, I will not release, someone else must be assigned.
> It is all near done, pack and upload should not be hard.
>
> I attach my working release_checklist as an orientation about what has been
> done and what needs to be done.
>
> While I will not be so much online in following days, I have no problem in
> answer lightweight questions about some build aspect.
>
> See.
>
> --
> claudio
>
> --
> You received this message because you are subscribed to the Google Groups
> "cocos2d discuss" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/cocos-discuss?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"cocos2d discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/cocos-discuss?hl=en.
