Yes, I am sorry about this.
I used the term release manager because I wanted to give Tom full
authority to do any replanning or rescheduling that he felt necessary in
my absence. The know-how of compiling the release are not so easily
transferred even though my ambition is that the "kit building
infrastructure" is in the argoumlinstaller project and fully documented
in the Cookbook. For this reason I didn't think this was possible in the
short term so I didn't bother to give Tom the key.
I am currently attempting to catch up on my mails and the plan still
looks like the plan still is to have a 0.22 tomorrow. I will be ready to
perform the release work by then.
/Linus
> -----Original Message-----
> From: Tom Morris [mailto:[EMAIL PROTECTED]
> Sent: den 31 juli 2006 18:56
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: [argouml-issues] [Issue 4386] Error trying to open file
> created with v 0.20
>
> > My understaning was that you are standing in as release
> > manager until Linus return. So a beta release could be made
> > very soon without delaying the final 0.22 release date of 8th
August.
>
> There should have been a very large set of quotes around the term
"release
> manager" when Linus used it. I don't have access to any of his
signing
> keys, his kit building machine or any of the other standard
infrastrcture.
> It would be much too high risk to try and recreate the whole kit
building
> infrastructure at this late date in the release cycle (and some
elements
> like the keys are not reproduceable).
>
> Any fixes committed now will turn the Aug. 8 kit into beta4 with the
final
> release some time after that (probably a week presuming no other
problems).
>
> Tom
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
