forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: release plan for 0.7
Date Fri, 10 Jun 2005 16:03:34 GMT
Ferdinand and i have spent a lot of time on skype today discussing
the nitty-gritty aspects of doing the release and made good progress.

As we already knew, one of the difficult parts of this release
is to get the website docs published properly. We think that we have
worked out a better solution and are going to develop that in a new branch.

We would like to move the code-freeze date to give us a bit more time.
There are also some personal reasons for each of us.

So the new code-freeze date is Monday 2005-06-13 at 14:00 UTC
but we will keep the release date the same.

Lazy consensus is in operation. Please speak up if you have
a problem with that change of plan, otherwise don't waste time
on replies.


David Crossley wrote:
> Here is my proposal for the release plan. If people have
> any concerns with the plan, then please raise them now.
> Code freeze and testing starts on Sunday 2005-06-12 at 14:00 UTC [1].
> During "code freeze" we cannot add any new functionality, just bug
> fixes and documentation tweaks [4].
> We create the release candidates for both Windows and UNIX on
> this day and start the vote. Don't bother voting until towards
> the end of the week, because we might need a new release candidate.
> If any changes have been made during the week [4] then we create
> another set of release candidates on Friday 2005-06-17 at 22:00 UTC [2]
> to give people time to verify the signatures and checksums and to do
> final tests. Between now and the release date there must no changes
> to SVN. If any are absolutely necessary, then we delay the release date
> and do another set of release candidates.
> Actual release date is Sunday 2005-06-19 at 14:00 UTC [3] then wait
> for the mirrors to receive it before sending the announcements.
> [1]
> [2]
> [3]
> [4] If committers make changes to SVN during code-freeze, then
> they must be made to both trunk and branch.
> --David

View raw message