On 2/3/20 5:15 AM, Richard Earnshaw (lists) wrote:
On 25/01/2020 16:11, Jeff Law wrote:
On Sat, 2020-01-25 at 10:50 -0500, Nathan Sidwell wrote:
On 1/24/20 4:36 PM, Jeff Law wrote:
On Fri, 2020-01-24 at 20:32 +0100, Eric Botcazou wrote:
I strongly prefer to move towards relying on the git log.
In my experience the output of git log is a total mess so cannot
replace
ChangeLogs. But we can well decide to drop ChangeLog for the
testsuite.
Well, glibc has moved to extracting them from git, building policies
and scripts around that. I'm pretty sure other significant projecs are
also extracting their ChangeLogs from git.
We could do the same, selecting some magic date as the cutover point
after which future ChangeLogs are extracted from GIT. In fact, that's
precisely what I'd like to see us do.
The GCC10 release date would seem a good point to do this. That
gives us around
3 months to figure the details (and get stakeholder buy-in)
Yup. That would be what I'd recommend we shoot for. As you say it
gives time to work on the details and for folks to start changing their
habits.
jeff
What about the maintained branches? Do they change as well? or would
they keep the existing ChangeLog files? If the latter, then backports
will need more care, but if the former, then the cut-over date needs
careful thought as they follow a different cadence.
I have a mild preference for release branches to follow trunk's
behaviour -- that's easier to remember. But, I don't look after a
release branch.
I'm not sure why you think the release cadence affects that? Just add a
top entry to all testsuite changelogs indicating it's no longer used.
Perhaps I'm missing something.
Other branches at the branch owner's discretion.
nathan
--
Nathan Sidwell
