This is the mail archive of the 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:

> On Fri, 11 Oct 2019, Florian Weimer wrote:
>> > My expectation for would be that the automatic ChangeLog generation is 
>> > always the last one before tagging and branching (so for future cycles 
>> > it's run for commits from the last release tag up to HEAD at that point, 
>> > whereas for this cycle the starting commit would be the point at which we 
>> > renamed the manually written ChangeLog, not the previous release tag).
>> We are debating off-list whether you are in favor of renaming the
>> ChangeLog *now*, or want to delay that to a future date.  Would you
>> please clarify?
> I support renaming it now, and making the wiki documentation of the 
> release process name the relevant commit as the starting point for 
> ChangeLog generation for the 2.31 release.

Thank you for the clarification.  Pushed.

I also added a lightweight tag, changelog-ends-here.  Thanks for the
suggestion that we shouldn't use an annotated tag for that.  I had to
tag directly on sourceware, to bypass the update hooks, that's why there
is no notification on glibc-cvs.  I verified that the non-annotated tag
is propagated by a git clone.


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