| Summary: | Eliminate changelogs | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | Tools / Tests | Assignee: | Jonathan Bedard <jbedard> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | angelos, jbedard, mcatanzaro, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 239082, 240759 | ||
|
Description
Michael Catanzaro
2022-04-12 07:40:23 PDT
> (a) Figure out a strategy for rolling changelogs anyway, e.g. WebKit repo administrators to do this themselves twice per year; or
Another option would be to add a label that is even more powerful than Unsafe-Merge-Queue, e.g. Skip-Merge-Queue or Roll-Changelogs. This would cause the queue to stop what it's doing and merge the PR immediately only if it is a fast-forward merge. Merge queue should never rebase anything labeled Skip-Merge-Queue/Roll-Changelogs, and should reject it if not a fast-forward merge.
I think it's probably not worth it, because I cannot think of any situation where this would be required except when rolling changelogs, and it'd be much nicer to archive and stop updating the changelogs.
> They are no longer useful: git commit messages should serve this purpose from now on.
The usefulness of ChangeLogs is that we can post inline comments for them during patch review.
This is not to say that my preference is to keep them; just stating as a fact.
Done now? Yeah, as of today we no longer use ChangeLogs. Re-opening for pull request https://github.com/WebKit/WebKit/pull/828 |