gcc-wwwdocs: Fix typo in GCC version number.
Checks
Commit Message
Noticed while trying to understand when I can expect the GCC 15 branch
to be created: the GCC 15 release criteria page still mentions GCC 14.
I'll push this as obvious.
Are such pages created via a script? If so I am happy to fix it as well.
---
htdocs/gcc-15/criteria.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
Comments
On Tue, 7 Jan 2025, Simon Martin wrote:
> Noticed while trying to understand when I can expect the GCC 15 branch
> to be created: the GCC 15 release criteria page still mentions GCC 14.
>
> I'll push this as obvious.
Thank you, Simon!
> Are such pages created via a script? If so I am happy to fix it as well.
Unless our release managers (Jakub on this case) have been taken over by
ChatGPT/Gemini/you-name-it I believe this is manual work following
https://gcc.gnu.org/releasing.html
though I just noticed criteria.html (and creating the directory for
the new release) isn't actually covered.
That could be a nice contribution to add...
Gerald
On Tue, 7 Jan 2025, Gerald Pfeifer wrote:
>> Are such pages created via a script? If so I am happy to fix it as well.
> Unless our release managers (Jakub on this case) have been taken over by
> ChatGPT/Gemini/you-name-it I believe this is manual work following
> https://gcc.gnu.org/releasing.html
> though I just noticed criteria.html (and creating the directory for
> the new release) isn't actually covered.
My bad: This is actually part of branching for a new release, which is
covered by
https://gcc.gnu.org/branching.html
Gerald
On Tue, Jan 07, 2025 at 11:20:11PM +0800, Gerald Pfeifer wrote:
> On Tue, 7 Jan 2025, Simon Martin wrote:
> > Noticed while trying to understand when I can expect the GCC 15 branch
> > to be created: the GCC 15 release criteria page still mentions GCC 14.
> >
> > I'll push this as obvious.
>
> Thank you, Simon!
>
> > Are such pages created via a script? If so I am happy to fix it as well.
>
> Unless our release managers (Jakub on this case) have been taken over by
I usually just git diff the branching or releasing commit from a year ago
and hand edit everything that clearly needs to be adjusted in the diff, then
apply.
In this case I've clearly failed to do parts of that.
> ChatGPT/Gemini/you-name-it I believe this is manual work following
> https://gcc.gnu.org/releasing.html
> though I just noticed criteria.html (and creating the directory for
> the new release) isn't actually covered.
>
> That could be a nice contribution to add...
Jakub
@@ -3,18 +3,18 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-<title>GCC 14 Release Criteria</title>
+<title>GCC 15 Release Criteria</title>
<link rel="stylesheet" type="text/css" href="https://gcc.gnu.org/gcc.css">
</head>
<body>
-<h1>GCC 14 Release Criteria</h1>
+<h1>GCC 15 Release Criteria</h1>
-<p>This page provides the release criteria for GCC 14.</p>
+<p>This page provides the release criteria for GCC 15.</p>
<p>The GCC team (and, in particular, the Release Managers) will attempt
-to meet these criteria before the release of GCC 14.</p>
+to meet these criteria before the release of GCC 15.</p>
<p>In all cases, these criteria represent the minimum functionality
required in order to make the release. If this level of minimum