Re: Update on GTK+-2.2.0 Final plans

[Owen Taylor <otaylor redhat com>]

General Status
=============

In general, we still seem to be in good shape; outside of 
win32 and GtkTreeView bugs on the 2.2.0 milestones are very
few and far between. The only code change I specifically plan 
to put in at this point is:

 http://bugzilla.gnome.org/show_bug.cgi?id=101318

Which adds endian-swap assembly for x86_64 and ia64 and should
have zero effect on other platforms. 

(There will most likely be a few more bug fixes that appear
this week.)

The -pthread/libtool/gcc bug:

 http://bugzilla.gnome.org/show_bug.cgi?id=100697

Is still a bit of a concern, but I don't really have 
any good ideas beyond what's currently in CVS, so I think
we'll ship that way.

Earlier today I moved all the GtkTextView bugs to 2.2.1; 
there's a lot of stuff there that needs fixing, but very 
little that's trivial to fix.

Kris and Jonathan have been busy elsewhere recently, so
we still have quite a few GtkTreeView bugs open on 2.2.0; 
the only class of bugs that I'm really concerned with is:

 - Regressions from 2.0 involving serious misbehavior or crashes.

If you know of such bugs, please bring it to my attention,
and I'll investigate and see what can be done.

Schedule Update
===============

 Tue December  3 

  - Glib-2.1.3, GTK+-2.1.3, Pango-1.1.4
  - Hard API freeze; no further API changes

 Fri December  6

  - Hard feature freeze, bug fixes only after this point
  - Identify critical bugs; punt low priority bugs to 2.2.1

 Mon December  9

  - Glib-2.1.4, GTK+-2.1.4, Pango-1.1.5

 Fri December 13 

  - Code freeze, after this point, only changes are:

    - Bug fixes for regressions from 2.2
    - Fixes for crashes and other major misbehavior

 Mon December 16 

   - Glib-2.1.5, GTK+-2.1.4, Pango-1.1.6; release candidates

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
We are here
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

 Fri December 20 - Final 2.2.0 release

The tarballs are all done now, I'll upload them and mail out
release announcements soon. It will take a bit more than
9 minutes (it is 11:51 PM now) but we are pretty much exactly 
on schedule.

Next step for me is to write up draft release announcments.

What I could use help with
==========================

 - Testing, testing, testing