Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Jul 8, 2025

Include the following checklist in your PR:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

Note: #10915 should be fixed by --with-repl.


This is an automatic backport of pull request #11033 done by Mergify.

* Add changelog files for 3.16

* Integrate Brandon’s suggestions.
* Integrate Brandon’s suggestions /II.
* Integrate Bodigrim’s suggestions.
* Integrate Artem’s suggestions.
  * Correctly capitalize “AArch” in preparation of #11047 backport
* Integrate Artem’s suggestions /II.

* Remove changelog.d bits

(cherry picked from commit 8b69517)
Copy link
Member

@Mikolaj Mikolaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To clarify, this is a "backport" from release branch to master branch, sometimes called a "forwardport".

@ffaf1
Copy link
Collaborator

ffaf1 commented Jul 9, 2025

Should I edit the title/patch message?

@ulysses4ever
Copy link
Collaborator

I'd say yes because the title is actively confusing at least for me.

@ffaf1 ffaf1 changed the title Backport #11033: Add 3.16 changelogs Forwardport #11033: Add 3.16 changelogs Jul 9, 2025
@ffaf1 ffaf1 added the release label Jul 9, 2025
@ffaf1
Copy link
Collaborator

ffaf1 commented Jul 10, 2025

I missed sweet merging window, this need manual resolution of conflicts, I will reopen a new one.

@ffaf1 ffaf1 closed this Jul 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants