gcc-7/changes.html and
gcc-7/index.html)
and ensure that they are all listed in contrib/gennews.
On the announcement page for that release series, note the new
release without removing information about any previous minor releases.
The changes.html page for that release series should have
details added of the changes in each minor release.java/jcf-dump.c, gcc.c,
gcov.c, fortran/gfortranspec.c and
gcov-dump.c (grep for "Copyright).
Also check documentation. See SVN revision 194838 for an incomplete
example.find . -name Makefile.in | xargs grep a+w
or
find . -name Makefile.in | xargs grep distdir:
might do the job.gcc.pot and cpplib.pot.maintainer-scripts/gcc_release script from the same
branch as the release. You must pass the -f option, to
indicate a final release, the -r option (for example,
-r 7.3.0), to give the release version, and, if diffs
against a previous release are to be generated, the -p
option, whose argument must name the .tar.xz file for a
previous release, in a directory containing all the
.tar.xz files for that previous release (for example,
-p /some/where/gcc-7.2.0/gcc-7.2.0.tar.xz)..sig files).gcc/BASE-VER.
gcc/DEV-PHASE remains empty. Check the file in.develop.html and releases.html
web pages.update_web_docs_git. The appropriate command to run (as gccadmin)
to generate the documentation would be scripts/update_web_docs_git
-r7.3.0 -dgcc-7.3.0 (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). Create additionally
onlinedocs/version-number/index.html by copying it
from a previous release and adjust it.maintainer-scripts/generate_libstdcxx_web_docs script on trunk.
That currently can't be done on sourceware.org due to dependencies on a
number of DocBook and LaTeX packages. The script takes two arguments, the
root of the GCC sources (for the new release) and the output directory
for the generated files. All the output that gets created should be placed
in the same onlinedocs/version-number/ directory
as the other documentation for the release.changes.html
to point to the online-documentation for the branch.index.html).maintainer-scripts/branch_changer.py script with the following arguments:
./maintainer-scripts/branch_changer.py api_key --new-target-milestone=10.4:10.5
--comment 'GCC 10.4 is being released, retargeting bugs to GCC 10.5.'
--limit N in order to limit the number of affected bugs.
Copyright (C) Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
These pages are maintained by the GCC team. Last modified 2026-07-21.