This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Move ChangeLog to ChangeLog.old/ChangeLog.19
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Tulio Magno Quites Machado Filho <tuliom at ascii dot art dot br>
- Cc: Siddhesh Poyarekar <siddhesh at gotplt dot org>, "Gabriel F. T. Gomes" <gabriel at inconstante dot net dot br>, Florian Weimer <fweimer at redhat dot com>, <libc-alpha at sourceware dot org>
- Date: Fri, 11 Oct 2019 19:57:13 +0000
- Subject: Re: [PATCH] Move ChangeLog to ChangeLog.old/ChangeLog.19
- Ironport-sdr: HAVBNj13G4ViKuD3x3J+AnEgatP3oD0sA8i850qPTDINuhlNEXiPRydBPRwtO/fM0lM8QFMz3B lvd7pOcP3Y+hLBLlqB8y3dhGLXDnvqIuDQBCDgQJPZ+G2k+6L0SoNcFC8Gu0AO92WzPi372kyz tS7CIHD2ll8n8F2YWKPnnTIQ04mjWqn9arXHGQlNbYLCLxrEmmTGG1frdMo3mC7cgFhdVSTJUi UncUHcpPBbcNCi28etOmASU/quQFQw6S5nbNgw0ez5KkaP6XACLFbKF3ExleCeXwfDn9eTop5s P7s=
- Ironport-sdr: F9d9GF+6qnNfs1HsXXVtmXqo5zgeCNBh2vxbt1rVWWnO/3tHlgWgImlW/iuz6e9VFZIJ+en9vG MIA4EKXK+5J/v+1Vz0BS1LV5h+Inedsejnz0UyOK4J4jbsV7gZbABXQ9Pvl83YE2kPSm0fodEg izhHZnIf3rWc8Vxk+gnlkO4p3RuVwQZYQy1KZj8zuFl5ru2Za46eaTPwjVVpS5CUM+Drh+3Zdq p6MmtX7efijdOVxdV5NiI5pQ5GzS6lpp1RL1T/gOYSKYh97Y4Vo9XkUdfzegyQRUst5CGYFIJU d4o=
- References: <87wode75tm.fsf@oldenburg2.str.redhat.com> <20191009102348.16dd1125@tereshkova> <alpine.DEB.2.21.1910091616280.19032@digraph.polyomino.org.uk> <fb543176-2552-e500-d82b-964467089949@gotplt.org> <87v9svw0oi.fsf@linux.ibm.com>
On Fri, 11 Oct 2019, Tulio Magno Quites Machado Filho wrote:
> I think this requires changes to the wiki page with the Release Process.
>
> Is this describing what you had in mind?
> https://sourceware.org/glibc/wiki/Release?action=diff&rev2=184&rev1=183
I think the new step should come *after* the updates to version.h and
features.h, just before tagging, so that those header updates appear at
the top of the generated ChangeLog.
I think the instructions will need to say explicitly what to use in place
of glibc-2.30 when generating the ChangeLog for 2.31.
After the second tag (the post-release one) has been created, there needs
to be a step of moving the generated ChangeLog to
ChangeLog.old/ChangeLog.<next-number>.
--
Joseph S. Myers
joseph@codesourcery.com