Status of 3.3.5 release and 3.3 branch

[Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>]

Hi Gaby,

what's up with the 3.3.5 release?

We've had several mails asking about the incomplete state of the 3.3.5
release:

http://gcc.gnu.org/ml/gcc/2004-10/msg00682.html
http://gcc.gnu.org/ml/gcc/2004-11/msg00064.html
http://gcc.gnu.org/ml/gcc/2004-11/msg00176.html
http://gcc.gnu.org/ml/gcc/2004-11/msg00193.html

But nothing has changed so far.
We also have patches for serious bug (wrong-code, ice-on-valid-code)
that should go into a future 3.3.6 relase, but the branch is still frozen.

I just went through releasing.html and half of the steps still
have to be done for the 3.3.5 release:

>   5.Upload the release to ftp.gnu.org.
GCC 3.3.3 is missing, too.

>   8.Update the releases.html and develop.html web pages. 
Only releases.html is incomplete.

>   9.Update the version numbers of the current and future releases on the main web page, and add a proper news item there as
>     well.
>  10.Add the release tag to the list in cvs.html (the branch tag should already be there). 

>  12.Generate online documentation for the new release with update_web_docs. The appropriate command to run (as
>     gccadmin) to generate the documentation would be scripts/update_web_docs -rgcc_3_0_2_release
>     -dgcc-3.0.2 (with the current version number inserted). Link to it from onlinedocs/index.html (but don't
>     break URLs to documentation for previous releases even if you remove the links to it). 

>  13.Update the main web page (index.html). 
This is covered under 9., I guess.

>  14.Announce the release to the gcc-announce@gcc.gnu.org and gcc@gcc.gnu.org mailing lists. 
>         Make sure that most mirrors have retrieved the new release already. 
>         In the case of a major release, coordinate announcements with the FSF. 
GCC 3.3.4 is missing as well.

>  15.Increment the version number in gcc/version.c, and put back the date stamp and (prerelease) annotation. Increment
>     the version number in doc/include/gcc-common.texi. 
>  16.Notify developers that checkins to the branch are once again allowed. 


>  20.Update the email parsing script to handle bugs against the new versions. The script is in CVS at
>     wwwdocs/bugzilla/contrib/bug_email.pl. Search for an existing version (like "3.3"), and update both places
>     it occurs to handle the new version through copy and paste.
GCC 3.2.3 is missing, too.


If you need help to complete the release, please say so, some tasks
could be performed by volunteers. But *please* do not leave release
and branch in such a dangling state. This is annoying users and developers.

Regards,
Volker