* Release notes for GCC 7? @ 2016-08-23 16:13 Joseph Myers 2016-08-23 20:20 ` Gerald Pfeifer 0 siblings, 1 reply; 7+ messages in thread From: Joseph Myers @ 2016-08-23 16:13 UTC (permalink / raw) To: gerald, gcc Is there a reason there's no changes.html for GCC 7 at this point? I'd presumed that when adding new features one should also write release notes for them (so, I should be writing release notes for _FloatN / _FloatNx), but the file hasn't yet been created and there are lots of other new features already in GCC 7 that need release notes. -- Joseph S. Myers joseph@codesourcery.com ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Release notes for GCC 7? 2016-08-23 16:13 Release notes for GCC 7? Joseph Myers @ 2016-08-23 20:20 ` Gerald Pfeifer 2016-08-24 7:35 ` Richard Biener 0 siblings, 1 reply; 7+ messages in thread From: Gerald Pfeifer @ 2016-08-23 20:20 UTC (permalink / raw) To: Joseph Myers; +Cc: gcc On Tue, 23 Aug 2016, Joseph Myers wrote: > Is there a reason there's no changes.html for GCC 7 at this point? None, apart from me missing it and http://gcc.gnu.org/releasing.html as well. Segher beat me to it now (I was planning to do it tonight); let me know whether there is anything else I can help with. > I'd presumed that when adding new features one should also write release > notes for them (so, I should be writing release notes for _FloatN / > _FloatNx) Yes, absolutely! That is the practice I always recommend. Gerald ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Release notes for GCC 7? 2016-08-23 20:20 ` Gerald Pfeifer @ 2016-08-24 7:35 ` Richard Biener 2017-03-12 22:45 ` PATCH for " Gerald Pfeifer 0 siblings, 1 reply; 7+ messages in thread From: Richard Biener @ 2016-08-24 7:35 UTC (permalink / raw) To: Gerald Pfeifer; +Cc: Joseph Myers, GCC Development On Tue, Aug 23, 2016 at 10:19 PM, Gerald Pfeifer <gerald@pfeifer.com> wrote: > On Tue, 23 Aug 2016, Joseph Myers wrote: >> Is there a reason there's no changes.html for GCC 7 at this point? > > None, apart from me missing it and http://gcc.gnu.org/releasing.html > as well. We've been creating those lazily over the last decade. We can change that, an entry for releasing.html is appreciated then so we don't forget. Richard. > Segher beat me to it now (I was planning to do it tonight); let me > know whether there is anything else I can help with. > >> I'd presumed that when adding new features one should also write release >> notes for them (so, I should be writing release notes for _FloatN / >> _FloatNx) > > Yes, absolutely! That is the practice I always recommend. > > Gerald ^ permalink raw reply [flat|nested] 7+ messages in thread
* PATCH for Re: Release notes for GCC 7? 2016-08-24 7:35 ` Richard Biener @ 2017-03-12 22:45 ` Gerald Pfeifer 2017-03-13 8:31 ` Richard Biener 0 siblings, 1 reply; 7+ messages in thread From: Gerald Pfeifer @ 2017-03-12 22:45 UTC (permalink / raw) To: Richard Biener; +Cc: Joseph Myers, gcc, gcc-patches On Wed, 24 Aug 2016, Richard Biener wrote: > We've been creating those lazily over the last decade. We can change > that, an entry for releasing.html is appreciated then so we don't forget. And here we go, in time for the release of GCC 7 / branching of GCC 8. (Except, this time I went ahead and already created gcc-8/changes.html so that you guys don't have to worry about that. ;-) Note, I added this to branching.html, not releasing.html, not the least since branching.html already had the creation of other web pages for the new release series and that also seems the more appropriate point time- wise. Agreed? Gerald Index: branching.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v retrieving revision 1.32 diff -u -r1.32 branching.html --- branching.html 28 Jun 2014 10:34:16 -0000 1.32 +++ branching.html 12 Mar 2017 22:37:59 -0000 @@ -7,6 +7,8 @@ <body> <p>This page documents the procedure for making a new release branch.</p> +<h2>Preparations</h2> + <ol> <li>Execute the following commands, substituting appropriate version numbers: @@ -38,15 +40,25 @@ for the next major release in the <code>wwwdocs</code> repository and populate it with initial copies of <code>changes.html</code> and <code>criteria.html</code>.</li> +</ol> -<li>Add <code>index.html</code> and <code>buildstat.html</code> pages -to the directory corresponding to the newly created release branch. -Update the toplevel <code>buildstat.html</code> accordingly.</li> +<h2>Web Site Updates</h2> + +<ol start="6"> +<li>Add <code>index.html</code> and <code>changes.html</code> pages +based on the previous release branch to the directory corresponding to +the newly created release branch.</li> + +<li>Add <code>buildstat.html</code> and update the toplevel +<code>buildstat.html</code> accordingly.</li> <li>Update the toplevel <code>index.html</code> page to show the new active release branch, the current release series, and active development (mainline). Update the version and development stage for mainline.</li> +</ol> +<ol start="9"> <li>Update <code>maintainer-scripts/crontab</code> on the mainline by adding an entry to make snapshots of the new branch and adjusting the version number of the mainline snapshots. @@ -67,7 +79,11 @@ <a href="translation.html#submit">Send them to the translation project</a> if no snapshot of this version was sent during development stage 3 or 4.</li> +</ol> +<h2>Bugzilla Updates</h2> + +<ol start="11"> <li>Create new versions in Bugzilla corresponding to the new mainline version. This can be accomplished by choosing "products", choosing "gcc", and editing the versions. Please do <strong>not</strong> delete old @@ -85,7 +101,6 @@ <li>Ask Daniel Berlin to adjust all PRs with the just-branched version in their summary to also contain the new version corresponding to mainline.</li> - </ol> </body> ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PATCH for Re: Release notes for GCC 7? 2017-03-12 22:45 ` PATCH for " Gerald Pfeifer @ 2017-03-13 8:31 ` Richard Biener 2017-03-27 8:13 ` carl hansen 0 siblings, 1 reply; 7+ messages in thread From: Richard Biener @ 2017-03-13 8:31 UTC (permalink / raw) To: Gerald Pfeifer; +Cc: Joseph Myers, GCC Development, GCC Patches On Sun, Mar 12, 2017 at 11:45 PM, Gerald Pfeifer <gerald@pfeifer.com> wrote: > On Wed, 24 Aug 2016, Richard Biener wrote: >> We've been creating those lazily over the last decade. We can change >> that, an entry for releasing.html is appreciated then so we don't forget. > > And here we go, in time for the release of GCC 7 / branching of GCC 8. > > (Except, this time I went ahead and already created gcc-8/changes.html > so that you guys don't have to worry about that. ;-) > > Note, I added this to branching.html, not releasing.html, not the least > since branching.html already had the creation of other web pages for the > new release series and that also seems the more appropriate point time- > wise. Agreed? Yes. Thanks, Richard. > Gerald > > > Index: branching.html > =================================================================== > RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v > retrieving revision 1.32 > diff -u -r1.32 branching.html > --- branching.html 28 Jun 2014 10:34:16 -0000 1.32 > +++ branching.html 12 Mar 2017 22:37:59 -0000 > @@ -7,6 +7,8 @@ > <body> > <p>This page documents the procedure for making a new release branch.</p> > > +<h2>Preparations</h2> > + > <ol> > <li>Execute the following commands, substituting appropriate version > numbers: > @@ -38,15 +40,25 @@ > for the next major release in the <code>wwwdocs</code> repository and > populate it with initial copies of <code>changes.html</code> and > <code>criteria.html</code>.</li> > +</ol> > > -<li>Add <code>index.html</code> and <code>buildstat.html</code> pages > -to the directory corresponding to the newly created release branch. > -Update the toplevel <code>buildstat.html</code> accordingly.</li> > +<h2>Web Site Updates</h2> > + > +<ol start="6"> > +<li>Add <code>index.html</code> and <code>changes.html</code> pages > +based on the previous release branch to the directory corresponding to > +the newly created release branch.</li> > + > +<li>Add <code>buildstat.html</code> and update the toplevel > +<code>buildstat.html</code> accordingly.</li> > > <li>Update the toplevel <code>index.html</code> page to show the new active > release branch, the current release series, and active development > (mainline). Update the version and development stage for mainline.</li> > +</ol> > > +<ol start="9"> > <li>Update <code>maintainer-scripts/crontab</code> on the mainline by > adding an entry to make snapshots of the new branch and adjusting the > version number of the mainline snapshots. > @@ -67,7 +79,11 @@ > <a href="translation.html#submit">Send them > to the translation project</a> if no snapshot of this version was sent > during development stage 3 or 4.</li> > +</ol> > > +<h2>Bugzilla Updates</h2> > + > +<ol start="11"> > <li>Create new versions in Bugzilla corresponding to the new mainline > version. This can be accomplished by choosing "products", choosing "gcc", > and editing the versions. Please do <strong>not</strong> delete old > @@ -85,7 +101,6 @@ > <li>Ask Daniel Berlin to adjust all PRs with the just-branched version > in their summary to also contain the new version corresponding to > mainline.</li> > - > </ol> > > </body> ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PATCH for Re: Release notes for GCC 7? 2017-03-13 8:31 ` Richard Biener @ 2017-03-27 8:13 ` carl hansen 2017-03-27 15:52 ` Joseph Myers 0 siblings, 1 reply; 7+ messages in thread From: carl hansen @ 2017-03-27 8:13 UTC (permalink / raw) To: Richard Biener; +Cc: Gerald Pfeifer, Joseph Myers, GCC Development, GCC Patches suggested additions: get and insert the latest libtool, which includes files: libtool.m4 ltgcc.m4 lt~obsolete.m4 ltoptions.m4 ltsugar.m4 ltversion.m4, all way-old currently in gcc-7 get latest autoconf. 2.64 in use, latest is 2.69 get latest texinfo.tex, not one 5 years old GNU is supposed to be a unified system, but it's not even up-to-date with its own software. I'm trying to debug a libtool bug but I am forced to downgrade autoconf... getting too hard to bother. It's not too late to fix it in gcc-7... On Mon, Mar 13, 2017 at 1:31 AM, Richard Biener <richard.guenther@gmail.com> wrote: > On Sun, Mar 12, 2017 at 11:45 PM, Gerald Pfeifer <gerald@pfeifer.com> wrote: >> On Wed, 24 Aug 2016, Richard Biener wrote: >>> We've been creating those lazily over the last decade. We can change >>> that, an entry for releasing.html is appreciated then so we don't forget. >> >> And here we go, in time for the release of GCC 7 / branching of GCC 8. >> >> (Except, this time I went ahead and already created gcc-8/changes.html >> so that you guys don't have to worry about that. ;-) >> >> Note, I added this to branching.html, not releasing.html, not the least >> since branching.html already had the creation of other web pages for the >> new release series and that also seems the more appropriate point time- >> wise. Agreed? > > Yes. > > Thanks, > Richard. > >> Gerald >> >> >> Index: branching.html >> =================================================================== >> RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v >> retrieving revision 1.32 >> diff -u -r1.32 branching.html >> --- branching.html 28 Jun 2014 10:34:16 -0000 1.32 >> +++ branching.html 12 Mar 2017 22:37:59 -0000 >> @@ -7,6 +7,8 @@ >> <body> >> <p>This page documents the procedure for making a new release branch.</p> >> >> +<h2>Preparations</h2> >> + >> <ol> >> <li>Execute the following commands, substituting appropriate version >> numbers: >> @@ -38,15 +40,25 @@ >> for the next major release in the <code>wwwdocs</code> repository and >> populate it with initial copies of <code>changes.html</code> and >> <code>criteria.html</code>.</li> >> +</ol> >> >> -<li>Add <code>index.html</code> and <code>buildstat.html</code> pages >> -to the directory corresponding to the newly created release branch. >> -Update the toplevel <code>buildstat.html</code> accordingly.</li> >> +<h2>Web Site Updates</h2> >> + >> +<ol start="6"> >> +<li>Add <code>index.html</code> and <code>changes.html</code> pages >> +based on the previous release branch to the directory corresponding to >> +the newly created release branch.</li> >> + >> +<li>Add <code>buildstat.html</code> and update the toplevel >> +<code>buildstat.html</code> accordingly.</li> >> >> <li>Update the toplevel <code>index.html</code> page to show the new active >> release branch, the current release series, and active development >> (mainline). Update the version and development stage for mainline.</li> >> +</ol> >> >> +<ol start="9"> >> <li>Update <code>maintainer-scripts/crontab</code> on the mainline by >> adding an entry to make snapshots of the new branch and adjusting the >> version number of the mainline snapshots. >> @@ -67,7 +79,11 @@ >> <a href="translation.html#submit">Send them >> to the translation project</a> if no snapshot of this version was sent >> during development stage 3 or 4.</li> >> +</ol> >> >> +<h2>Bugzilla Updates</h2> >> + >> +<ol start="11"> >> <li>Create new versions in Bugzilla corresponding to the new mainline >> version. This can be accomplished by choosing "products", choosing "gcc", >> and editing the versions. Please do <strong>not</strong> delete old >> @@ -85,7 +101,6 @@ >> <li>Ask Daniel Berlin to adjust all PRs with the just-branched version >> in their summary to also contain the new version corresponding to >> mainline.</li> >> - >> </ol> >> >> </body> ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PATCH for Re: Release notes for GCC 7? 2017-03-27 8:13 ` carl hansen @ 2017-03-27 15:52 ` Joseph Myers 0 siblings, 0 replies; 7+ messages in thread From: Joseph Myers @ 2017-03-27 15:52 UTC (permalink / raw) To: carl hansen; +Cc: Richard Biener, Gerald Pfeifer, GCC Development, GCC Patches On Mon, 27 Mar 2017, carl hansen wrote: > suggested additions: > > get and insert the latest libtool, which includes files: > libtool.m4 ltgcc.m4 lt~obsolete.m4 ltoptions.m4 ltsugar.m4 ltversion.m4, > all way-old currently in gcc-7 libtool and auto* updates are only reasonable in development stage 1. They are highly riskly changes that require extensive testing in a range of native, cross and Canadian cross configurations. (And a reminder of the need to revert libtool commit 3334f7ed5851ef1e96b052f2984c4acdbf39e20c, see <https://gcc.gnu.org/ml/gcc-patches/2011-01/msg00520.html>.) -- Joseph S. Myers joseph@codesourcery.com ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2017-03-27 15:52 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2016-08-23 16:13 Release notes for GCC 7? Joseph Myers 2016-08-23 20:20 ` Gerald Pfeifer 2016-08-24 7:35 ` Richard Biener 2017-03-12 22:45 ` PATCH for " Gerald Pfeifer 2017-03-13 8:31 ` Richard Biener 2017-03-27 8:13 ` carl hansen 2017-03-27 15:52 ` Joseph Myers
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).