CDT 11.0.0 about cdt

[jonahgraham]

As discussed at our last call, I planned to prepare a draft release with plenty of time before the CDT 11.0.0 release.

The release is next Wednesday (Dec 7th).

Committers should be able to see the CDT 11.0.0 draft release here: https://github.com/eclipse-cdt/cdt/releases (please edit as you see fit, but do not publish it). PS I can't confirm that anyone else can see it, perhaps only I can see the draft?

In addition I added a link to a GitHub search for noteworthy issues and PRs to the N&N document:
https://github.com/eclipse-cdt/cdt/blob/main/NewAndNoteworthy/CDT-11.0.md#noteworthy-issues-and-pull-requests

Please comment here on the issue with your thoughts.

[jld01]

Hi @jonahgraham, do you think it's preferable/valuable to list the full set of PRs for milestone 11.0.0 on the release anouncement page as opposed to just the noteworthy PRs? Many of the non-noteworthy PRs will be of little interest to typical readers of the announcement. A counterargument is that every PR represents someone's effort towards the release and should be recognized.

[jonahgraham]

I had a similar thought - I like the autogenerated part(0), especially the New Contributors section(1). But I found it to be of little value(2), which is why I hid it behind the collapsible section(3).

(0) I imagine that as GitHub evolves the autogeneration will get more interesting too.

(1) In this release the "new contributors" section is a little off because we just moved to GitHub. You, me and @Torbjorn-Svensson aren't listed because we are listed in the 10.7.1 release page

(2) I agree with you about the value of recognizing someone's contribution. It can be a nice ego boost to see your name/contribution listed up front like that. The other value is it shows life of the project a little, similar purpose to the charts on PMI

PS I don't want to spend time manually maintaining a list. I think it is the auto-generated list, a link to the search, or I copy and paste the N&N into the release page.

[jonahgraham]

Update or create composites in preparation for going public on release day

I made a mistake in the above step, which is fixed in fb081b9 but there is caching on download.eclipse.org which the p2 repo will present as slightly broken until the caches catch up.

They seem to be caught up for me already, but the GitHubActions seems to be seeing the old versions

[jonahgraham]

CDT 11.0.0 is done, onto CDT 11.1.0 in #202

PS. If we need a CDT 11.0.1 we can create that at short notice.