>
3. LF specifies an official release date and begins the irreversible press release process
It’s not exactly like this.
Typically we would agree a date for pre-briefing journalists and the release going to the wire (it’s like an aggregator for journalists)
When that date has passed (probably in reality a day before with time-zone issues), there cannot be a change.
Ideally, you don’t want to have to re-schedule press briefings with journalists either.
Regards
Lars
From: George Dunlap [mailto:george.dunlap@xxxxxxxxxxxxx]
Sent: 24 February 2014 18:31
To: Sarah Conway
Cc: Russell Pavlicek; Lars Kurth; publicity@xxxxxxxxxxxxxxxxxxxx
Subject: Re: Release
OK, cool. As it happens, I don't think we need to delay anything on our side; and as we've branched, development isn't being held up -- so no rush.
Just to understand the general process, my understanding was:
1. Development and release preparation happen in parallel
2. Developers determine that a release is ready
3. LF specifies an official release date and begins the irreversible press release process
4. The release happens on the specified date
Lars made it clear that once #3 happened, #4 basically had to happen at the specified date no matter what. Which means that, we need to make sure that there is a coordination between us to make sure that #3 doesn't happen until #2 happens. :-)
At the moment, we're good to go on our side -- but before you actually start #3, it would be good to touch base with us to make sure we haven't changed our minds again.
Is that about right?
-George
On 02/24/2014 06:01 PM, Sarah Conway wrote:
Yes, in fact that is preferred. Planning to send out a revised release with a timeline of next steps.
On Mon, Feb 24, 2014 at 10:42 AM, George Dunlap <george.dunlap@xxxxxxxxxxxxx> wrote:
Sarah,
We've just found a couple of bugs in the RC5. What's the situation re the press release? I haven't heard from you, so I assume that we haven't hit the point of no return yet -- if we needed to delay the release for another week, we could?
Thanks,
-George
--
