Re: GNOME 2.0 Schedule

[Stephen Browne <stephen browne sun com>]

Just some thoughts on this schedule.

So we now have a schedule, we have a list of things that have been done so far
and the status of libs in the 2.0 platform, but do we have any idea of what is
left to
do to make up a deliverable Gnome 2.0 user desktop?

Do we have any idea of the scope of work that still needs to be done?
Do we know how many people are going to be working on it?
Do we have a commitment from module maintainers to do the port?
(I'm thinking about core things here like the control center,
see recent mails on gnomecc-list)

I guess I just get the impression that things are still a little
disorganised, not everyone is focusing on Gnome 2.0.

I suppose the release co-ordinators must have the answers to
these questions since the schedule should reflect them so I
was wondering if they could share.

Stephen

Maciej Stachowiak wrote:

> As promised, here is the schedule for GNOME 2.0. We will try to get
> this on the web site soon.
>
> Oct. 24 Package List FREEZE - package list for Gnome 2.0 finalized
>
> Oct. 31 PACKAGES DUE - Gnome 2. Platform Alpha 2
> Nov. 2  RELEASE - Gnome 2.0 Platform Alpha 2
>
> Nov. 2  API FREEZE - any further API changes must be individually approved [1]
>
> Nov. 23 Feature FREEZE - no feature additions for core packages w/o approval
>         of release team [1]
>
> Dec. 5  PACKAGES DUE - Gnome 2.0 Beta 1
> Dec. 7  RELEASE - Gnome 2.0 Beta 1
>
> Dec. 21 UI FREEZE - no more UI changes w/o approval of release  team [1]
>
> Jan. 2  PACKAGES DUE - Gnome 2.0 Beta 2  [2]
> Jan. 4  RELEASE - Gnome 2.0 Beta 2
>
> Jan. 16 String FREEZE - no more localizable string changes w/o approval of
>         release team [1]
>
> Jan. 23 PACKAGES DUE - Gnome 2.0 Release Candidate 1
> Jan. 25 RELEASE - Gnome 2.0 Release Candidate 1
>
> Jan. 25 Deep FREEZE - release team approved fixes only from now to final [1]
>
> Feb. 13 PACKAGES DUE - Gnome 2.0 final
> Feb. 15 RELEASE - Gnome 2.0 final  [2]
>
> Notes:
>
> [1] The GNOME 2 release team will be enforcing the various freeze
> dates. If you have a change that breaks one of the freezes but that
> you feel must go in, please contact us so we can review the change.
>
>   We will be much more likely to accept changes that are planned
> before the freeze date but don't quite make it, or changes that are
> agreed upon by all affected parties.
>
>   We all need to do our best to make these freeze dates to get the
> release out on time.
>
> [2] If you will be away around this date (or other package due dates),
> you must get your packages in early or designate someone else to do
> make a release.
>
> _______________________________________________
> gnome-2-0-list mailing list
> gnome-2-0-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-2-0-list


_______________________________________________
gnome-hackers mailing list
gnome-hackers gnome org
http://mail.gnome.org/mailman/listinfo/gnome-hackers