Release 1.33 meta tasks

[callahad]

• Review all open PRs
• Ensure changelog is up to date, select shortlist of user-facing changes to highlight (@avahahn + @ac000)
• Write up user-facing highlights (@Jcahilltorre)
• Review the commits immediately prior to 1.32 to see if there are any steps we might miss (@ac000)
• Update wasmtime version for the wasm-wasi-component language module (@avahahn)
• Re-review the release checklist (@callahad)

...and then hand it off to SysEng to make the release :)

[Jcahilltorre]

Where can I see the list of items to be highlighted on this release?

[callahad]

Those will be plucked out by @avahahn and @ac000 as part of the bullet immediately above the handoff task :)

[ac000]

OK, forget the previous comment.

To keep just one source of truth (docs/changes.xml/CHANGES), I've started #1401

[ac000]

As well as the changelog, I think we should start providing the output of git shortlog ... as the Git (and other projects do), e.g https://lore.kernel.org/git/[email protected]/

And let's not forget to highlight our external contributors... currently

Alejandro Colomar (12)
Arjun (15)
Costas Drongos (1)
Gourav (2)
Remi Collet (1)
dependabot[bot] (5)

I think we can ignore dependabot!

[ac000]

We should probably give Arjun (@pkillarjun) special mention for his fuzzing work...

[ac000]

In terms of what we need to commit before a release, looking back over the last few releases, there's no standard order of things, but I believe it should basically be these three commits

1. Generate dockerfiles (well that's what it was called ace553d) Update dockerfiles
2. Update changes.xml
3. Generate new CHANGES files

That last commit is what gets tagged as the new release.

Except that the dockerfile thing throws a slight fly in the ointment due to changes like

-    && git clone --depth 1 -b 1.31.1-1 https://github.com/nginx/unit \
+    && git clone --depth 1 -b 1.32.0-1 https://github.com/nginx/unit \

Which means there is a window (albeit small(ish)) where these won't work until the -1 tag is created.

It also looks like we can just get rid of .hgtags, that hasn't been updated since 1.31.1

[Jcahilltorre]

I will open a PR with the skeleton file for the news page

[ac000]

I have created a draft of the 1.33.0 announce email (sent to the Unit mailing list), somewhat inspired by git's announce emails.

If anyone notices their favourite feature missing, let me know, or even better, send text!

@Jcahilltorre Feel free to lift bits out of there for the website.

[ac000]

Hey folks, still a few outstanding things before we can release...

• ci: Fix tags on ad hoc unitctl releases #1337
  @callahad Do you want to merge this or have someone else do it?

• tests: Fix `/status' endpoint to cater for lists #1371
  Still requires a review...

• ci: Enable the wasm-wasi-component tests #1402
  This needs a review and would be good to merge before the below wasm-wasi-component updates

• Upgrade wasm-wasi-component to latest Wasmtime #1392
  @avahahn @javorszky AIUI this is done?, but needs a pull-request and review
  Once that is done, I plan to merge (assuming it just works) the fix for

• BUG: Environment Variables not passed to Wasm Applications #1312