3.0.9 3.0.10 release notes

[d-v-b]

This PR removes the changelogs and adds the release notes for our backported releases (3.0.9 and 3.0.10). This ensures that our next release off main (which hopefully is 3.1.0) has an accurate set of release notes.

[dstansby]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

[d-v-b]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

that's a good idea!

[dstansby]

I think you've merged main into this branch (3.0.9-3.0.10-release-notes), instead of merging the 3.0.10 branch into this branch?

[d-v-b]

the 3.0.10 branch has commits from backported PRs, I'm not sure we want that in main

[dstansby]

That should be fine - the commit history is merged in, but the code changes don't apply because they're already on main. I had a go here: #3220

[dstansby]

Hmm, all I did in #3220 was a single merge command, and there's 12 deleted changelog files. But here there's 17 deleted files... I wonder which one is correct?

[dstansby]

Ah, it was because I needed to merge 3.0.9 in too.

[d-v-b]

closing as redundant due to #3220

[d-v-b]

This PR removes the changelogs and adds the release notes for our backported releases (3.0.9 and 3.0.10). This ensures that our next release off main (which hopefully is 3.1.0) has an accurate set of release notes.

[dstansby]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

[d-v-b]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

that's a good idea!

[dstansby]

I think you've merged main into this branch (3.0.9-3.0.10-release-notes), instead of merging the 3.0.10 branch into this branch?

[d-v-b]

the 3.0.10 branch has commits from backported PRs, I'm not sure we want that in main

[dstansby]

That should be fine - the commit history is merged in, but the code changes don't apply because they're already on main. I had a go here: #3220

[dstansby]

Hmm, all I did in #3220 was a single merge command, and there's 12 deleted changelog files. But here there's 17 deleted files... I wonder which one is correct?

[dstansby]

Ah, it was because I needed to merge 3.0.9 in too.

[d-v-b]

closing as redundant due to #3220

[d-v-b]

This PR removes the changelogs and adds the release notes for our backported releases (3.0.9 and 3.0.10). This ensures that our next release off main (which hopefully is 3.1.0) has an accurate set of release notes.

[dstansby]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

[d-v-b]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

that's a good idea!

[dstansby]

I think you've merged main into this branch (3.0.9-3.0.10-release-notes), instead of merging the 3.0.10 branch into this branch?

[d-v-b]

the 3.0.10 branch has commits from backported PRs, I'm not sure we want that in main

[dstansby]

That should be fine - the commit history is merged in, but the code changes don't apply because they're already on main. I had a go here: #3220

[dstansby]

Hmm, all I did in #3220 was a single merge command, and there's 12 deleted changelog files. But here there's 17 deleted files... I wonder which one is correct?

[dstansby]

Ah, it was because I needed to merge 3.0.9 in too.

[d-v-b]

closing as redundant due to #3220

[d-v-b]

This PR removes the changelogs and adds the release notes for our backported releases (3.0.9 and 3.0.10). This ensures that our next release off main (which hopefully is 3.1.0) has an accurate set of release notes.

[dstansby]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

[d-v-b]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

that's a good idea!

[dstansby]

I think you've merged main into this branch (3.0.9-3.0.10-release-notes), instead of merging the 3.0.10 branch into this branch?

[d-v-b]

the 3.0.10 branch has commits from backported PRs, I'm not sure we want that in main

[dstansby]

That should be fine - the commit history is merged in, but the code changes don't apply because they're already on main. I had a go here: #3220

[dstansby]

Hmm, all I did in #3220 was a single merge command, and there's 12 deleted changelog files. But here there's 17 deleted files... I wonder which one is correct?

[dstansby]

Ah, it was because I needed to merge 3.0.9 in too.

[d-v-b]

closing as redundant due to #3220

[d-v-b]

This PR removes the changelogs and adds the release notes for our backported releases (3.0.9 and 3.0.10). This ensures that our next release off main (which hopefully is 3.1.0) has an accurate set of release notes.

[dstansby]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

[d-v-b]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

that's a good idea!

[dstansby]

I think you've merged main into this branch (3.0.9-3.0.10-release-notes), instead of merging the 3.0.10 branch into this branch?

[d-v-b]

the 3.0.10 branch has commits from backported PRs, I'm not sure we want that in main

[dstansby]

That should be fine - the commit history is merged in, but the code changes don't apply because they're already on main. I had a go here: #3220

[dstansby]

Hmm, all I did in #3220 was a single merge command, and there's 12 deleted changelog files. But here there's 17 deleted files... I wonder which one is correct?

[dstansby]

Ah, it was because I needed to merge 3.0.9 in too.

[d-v-b]

closing as redundant due to #3220

[d-v-b]

This PR removes the changelogs and adds the release notes for our backported releases (3.0.9 and 3.0.10). This ensures that our next release off main (which hopefully is 3.1.0) has an accurate set of release notes.

[dstansby]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

[d-v-b]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

that's a good idea!

[dstansby]

I think you've merged main into this branch (3.0.9-3.0.10-release-notes), instead of merging the 3.0.10 branch into this branch?

[d-v-b]

the 3.0.10 branch has commits from backported PRs, I'm not sure we want that in main

[dstansby]

That should be fine - the commit history is merged in, but the code changes don't apply because they're already on main. I had a go here: #3220

[dstansby]

Hmm, all I did in #3220 was a single merge command, and there's 12 deleted changelog files. But here there's 17 deleted files... I wonder which one is correct?

[dstansby]

Ah, it was because I needed to merge 3.0.9 in too.

[d-v-b]

closing as redundant due to #3220

[d-v-b]

This PR removes the changelogs and adds the release notes for our backported releases (3.0.9 and 3.0.10). This ensures that our next release off main (which hopefully is 3.1.0) has an accurate set of release notes.

[dstansby]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

[d-v-b]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

that's a good idea!

[dstansby]

I think you've merged main into this branch (3.0.9-3.0.10-release-notes), instead of merging the 3.0.10 branch into this branch?

[d-v-b]

the 3.0.10 branch has commits from backported PRs, I'm not sure we want that in main

[dstansby]

That should be fine - the commit history is merged in, but the code changes don't apply because they're already on main. I had a go here: #3220

[dstansby]

Hmm, all I did in #3220 was a single merge command, and there's 12 deleted changelog files. But here there's 17 deleted files... I wonder which one is correct?

[dstansby]

Ah, it was because I needed to merge 3.0.9 in too.

[d-v-b]

closing as redundant due to #3220

[d-v-b]

This PR removes the changelogs and adds the release notes for our backported releases (3.0.9 and 3.0.10). This ensures that our next release off main (which hopefully is 3.1.0) has an accurate set of release notes.

[dstansby]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

[d-v-b]

Instead of doing it manually, might be nicer for the commit history/branches to merge the 3.0.10 branch into main?

that's a good idea!

[dstansby]

I think you've merged main into this branch (3.0.9-3.0.10-release-notes), instead of merging the 3.0.10 branch into this branch?

[d-v-b]

the 3.0.10 branch has commits from backported PRs, I'm not sure we want that in main

[dstansby]

That should be fine - the commit history is merged in, but the code changes don't apply because they're already on main. I had a go here: #3220

[dstansby]

Hmm, all I did in #3220 was a single merge command, and there's 12 deleted changelog files. But here there's 17 deleted files... I wonder which one is correct?

[dstansby]

Ah, it was because I needed to merge 3.0.9 in too.

[d-v-b]

closing as redundant due to #3220