Add 3.10.1.0 changelogs and remove the used up tiny changlog files

[Mikolaj]

The remaining chagelog files are indeed those we haven't managed to fit it. I haven't checked if the removed files match what's in the changelog documents themselves nor did I check all the PRs mentioned in the changelog-d utility warnings (https://paste.tomsmeding.com/N5YLPa58; many or most of which seem to be false positives).

I've created the files strictly following https://github.com/haskell/cabal/wiki/Making-a-release

[ulysses4ever]

I'm not a big fan of repeating important changes to Cabal in cabal-install changelog: they're already out of sync (besides, I'm not sure it's all that helpful).

[Mikolaj]

I'm not a big fan of repeating important changes to Cabal in cabal-install changelog: they're already out of sync (besides, I'm not sure it's all that helpful).

Sure. But I suggest we should rather educate PR authors (and improve our CONTRIBUTING material) than patch the changelogs. Please open a ticket about it if you have a short outline of the policy change we could enact.

[ulysses4ever]

Sure. But I suggest we should rather educate PR authors (and improve our CONTRIBUTING material) than patch the changelogs. Please open a ticket about it if you have a short outline of the policy change we could enact.

Mm, perhaps I didn't get what this means:

• Cabal-3.10.1.0 is used, which brings its own set of changes,
  many of which are significant. The Cabal and Cabal-syntax changes that touch
  the cabal-install or cabal-install-solver codebases are pasted here again in full.

I meant the "pasted" bit. Can we not paste anything that has already been said somewhere? It's a way to disaster usually. But if it's a consequence of people putting "component: Cabal, cabal-install" in the changelogs, than I don't suggest we add even more work for the release and remove them manually.

[Mikolaj]

I meant the "pasted" bit. Can we not paste anything that has already been said somewhere? It's a way to disaster usually. But if it's a consequence of people putting "component: Cabal, cabal-install" in the changelogs, than I don't suggest we add even more work for the release and remove them manually.

Oh, yes, I meant 'pasted by the changelog-d utility due to users saying "component: Cabal, cabal-install"'. I haven't pasted anything manually. I'm lazy. I also haven't removed manually (almost) anything.

[Mikolaj]

github marks some of my comments as Pending, so let me see if finishing a review fixes that

Edit: it did.

Edit2: though the comments are misplaced. Let me copy them where they belong.

Edit3: oh no, they are already copied there.

[ulysses4ever]

@Mikolaj how about pulling up haddock-project to the list of significant changes?

[Mikolaj]

@Mikolaj how about pulling up haddock-project to the list of significant changes?

Right. Done.

[Mikolaj]

@mergify backport 3.10

[mergify]

backport 3.10

❌ No backport have been created

• Backport to branch 3.10 failed

Git reported the following error:

To https://github.com/haskell/cabal
 ! [rejected]            mergify/bp/3.10/pr-8831 -> mergify/bp/3.10/pr-8831 (non-fast-forward)
error: failed to push some refs to 'https://github.com/haskell/cabal'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

[Mikolaj]

let me speed up the merging of cabal 3.10 changelogs so that we have candidates ready for tomorrows dev's meeting

[Mikolaj]

@mergify backport 3.10

[mergify]

backport 3.10

❌ No backport have been created

• Backport to branch 3.10 failed

Git reported the following error:

To https://github.com/haskell/cabal
 ! [rejected]            mergify/bp/3.10/pr-8831 -> mergify/bp/3.10/pr-8831 (non-fast-forward)
error: failed to push some refs to 'https://github.com/haskell/cabal'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

[Mikolaj]

@mergify rebase

[Mikolaj]

@mergify backport 3.10

[mergify]

rebase

☑️ Nothing to do

• -closed [:pushpin: rebase requirement]

[mergify]

backport 3.10

❌ No backport have been created

• Backport to branch 3.10 failed

Git reported the following error:

To https://github.com/haskell/cabal
 ! [rejected]            mergify/bp/3.10/pr-8831 -> mergify/bp/3.10/pr-8831 (non-fast-forward)
error: failed to push some refs to 'https://github.com/haskell/cabal'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

[andreasabel]

let me speed up the merging of cabal 3.10 changelogs so that we have candidates ready for tomorrows dev's meeting

@Mikolaj : Sorry, I am travelling atm, so I missed the meeting and the latest action here. Hope you got the necessary feedback yesterday.

[Mikolaj]

Yes, @andreasabel, we are fine. :) Have a great trip!