GDB: The GNU Project Debugger

Release schedule for GDB

Problems that should be resolved before the next release are marked as ``high priority'' in the bug database.

GDB's schedule works on a slip-for-slip basis. If, for some reason, the branch date slips, the release date will slip by an equivalent amount.

Release	Estimate	Schedule	Actual	Slip (months)	Comment
6.3	2004-11	2004-11	2004-11-09	0!	We rock!
6.2	2004-08	2004-07-30	2004-07-30	0	Went very smootly (provided you ignore that MIPS was discovered to be broken on the last day).
6.1.1	2004-05	2004-05-31	2004-06-16	1	Kept NEWS entries missed in 6.1.
6.1	2004-01	2004-03-27	2004-04-04	2	Branched two months late (slight distraction). Need to ensure that only bug fixes get committed to the branch.
6	2003-03	2003-08-26	2003-10-06	2	The estimated branch date was 2003-03-01-gmt, but in the end it was scheduled for 2003-06-14-gmt. Once on the branch, a very small list of must-have features draged things out. Adding to the fun, at the last moment the process hit unanticipated non-coding problems causing the cart wheels to fall off :-)
5.3		2002-10-09	2002-12-12	2	Branched on time. Released late. Too many things to cleanup on the branch.
5.2.1		2002-06-16	2002-07-23	1	Scheduled too soon after previous release
5.2		2002-04-07	2002-04-30	1
5.1.1		2002-01-24	2002-01-24
5.1		2001-08-05	2001-11-21	3	Unscheduled (human) breakage
5		2000-02-29	2000-05-19	3	Too ambitious
4.18		1999-04-10

Please send FSF & GNU inquiries & questions to gnu@gnu.org. There are also other ways to contact the FSF.

This page is maintained by the GDB developers.

Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.

Last modified 2006-01-20.