Re: Imminent API/ABI freeze: (was TARBALLS DUE: GNOME 2.5.1 Developme nt Release)
Bill Haneman <Bill.Haneman <at> Sun.COM>
2003-12-04 13:54:52 GMT
Murray.Cumming <at> Comneon.com wrote:
Just so you can't say we didn't warn you, I'd like to point out that the
API/ABI freeze will happen on December 8th, 4 days from now.
Murray/all:
Just so you know - there is a _critical_ accessibility API-related bug
in gtk+ which haven't been addressed yet, since Owen has been on
holiday (and several other serious accessibility API bugs against
gtk+). I don't know quite what to do about this, but at least one of
the bugs is a total accessibility stopper and as such may have to be
dealt with via an exception to the freeze:
64613
The user-visible problem is GOK bug
126727
|
cri |
Urg |
REOP |
|
gok |
general |
GOK getting focus due to gtk+ internals change |
but this bug cannot be fixed or worked around in GOK.
This (like several accessibility problems in the GNOME 2.5 stack) is
caused by behavioral changes in gtk+, so from a user viewpoint they are
very serious regressions. However from gtk+'s viewpoint bincompat has
not been broken, so the only alternative is either change gtk+'s
behavior or new API. There's a patch for the gtk+ bug, but if it can't
be applied the only alternative is new API.
There is also gnomeprint bug
We've been trying to deal with this one and will work with Jody to try
and solve it by Monday - but it's definitely an API issue.
We have been working hard to close all the API issues in the
accessibility modules on time, but some issues cannot be resolved in
the accessibility modules themselves.
Other significant gtk+ API issues for accessibility:
Of these, three have patches which have not been reviewed.
How should we proceed to get these resolved in time?
regards
Bill
Here's some information about the API/ABI freeze:
http://developer.gnome.org/dotplan/tasks.html#FreezeAPI
http://developer.gnome.org/dotplan/tasks.html#ApprovingFreezeBreaks
As ever, we would like you to send an email to the release-team to tell us
what new API you have added to your GNOME Platform modules.
Here's a pretty calendar to scare your pants off:
December 2003
Su Mo Tu We Th Fr Sa
1 2 3 4 5 6
7 (8) 9(10)11 12 13 2.5.1, API/ABI Freeze
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28(29)30(31) 2.5.2 tarballs due and released
January 2004
Su Mo Tu We Th Fr Sa
1 2 3
4 5 6 7 8 9 10
11(12)13(14)15 16 17 2.5.3, Feature, Module and UI Freeze
18 19 20 21 22 23 24
25(26)27(28)29 30 31 2.5.4 tarballs due and released
February 2004
Su Mo Tu We Th Fr Sa
1 2 3 4 5 6 7
8 (9)10(11)12 13 14 Beta 1, String and Hard UI Freeze
15 16 17 18 19 20 21
22(23)24(25)26 27 28 Beta 2, HARD CODE FREEZE
29
March 2004
Su Mo Tu We Th Fr Sa
(1) 2 (3) 4 5 6 Release Candidate tarballs due and released
7 (8) 9(10)11 12 13 GNOME 2.6.0 FINAL
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31
Murray Cumming
www.murrayc.com
murrayc <at> usa.net
_______________________________________________
gnome-hackers mailing list
gnome-hackers <at> gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-hackers