This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Move ChangeLog to ChangeLog.old/ChangeLog.19


Joseph Myers <joseph@codesourcery.com> writes:

> 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.

Ack.

> 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.

I didn't understand your proposal.
What do you think that needs to be explicit in this example for glibc 2.31?

    ./scripts/gitlog_to_changelog.py glibc-2.30 HEAD > ChangeLog

> 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>.

Ack.

-- 
Tulio Magno


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]