Release: Publish Gitea 1.22

[lunny]

1.22.0

Release 1.22.0 in one week if rc1 is stable enough.

• Prepare a new changelog (there are a lot of new changes) and update CHANGELOG.md Add v1.22.0 changelog #31060
• Release 1.22.0 from release/v1.22 branch
  • Generate changelog_1.22.0.md from merged CHANGELOG.md
  • Tag 1.22.0 with git tag -s -f changelog_1.22.0.md v1.22.0-rc1 and Push to Github
  • Wait for the release created and check whether the release artifacts generated
    • Check whether Github release attachments are generated and normal
    • Check whether the binaries generated under https://dl.gitea.com/gitea/1.22.0/ and normal
    • Check whether docker images are generated https://hub.docker.com/r/gitea/gitea/tags?page=&page_size=&ordering=&name=1.22.0
  • If the release does work then make it out of draft so that it's public for everyone.
• Update "version.json" to 1.22.0
• Update documentation's latest stable version to 1.22.0
• Update API documentation latest stable version to 1.22.0
• Confirm blog is ready and merge it https://gitea.com/gitea/blog/pulls/372
• Announce the 1.22.0 release.

1.22.0-rc1 (Done)

• Rename v1_23 migrations to v1_22
• Move merged PRs from 1.23 to 1.22 milestone
  • If a PR isn't in 1.22-legacy (no backport/done): move it to 1.22 milestone
  • If a PR is in 1.22-legacy: add "skip-changelog" to it and leave it in 1.23 milestone
• Close unnecessary legacy 1.22 backports
• Release 1.22.0-rc1 from main branch
  • Create release/v1.22-legacy from old release/v1.22
  • Create the new release/v1.22 from the main branch and force push to Github.
  • Tag 1.22-rc1 with git tag -s -m "Second release candidate for 1.22.0" v1.22.0-rc1 and Push to Github
  • Wait for the release created and check whether the release artifacts generated
    • Check whether Github release attachments are generated and normal
    • Check whether the binaries generated under https://dl.gitea.com/gitea/1.22.0-rc1/ and normal
    • Check whether docker images are generated https://hub.docker.com/r/gitea/gitea/tags?page=&page_size=&ordering=&name=1.22.0-rc1
  • If the release does work then make it out of draft so that it's public for everyone.
• Update documentation to upgrade from v1.22-rc0 -> v1.22-rc1 https://gitea.com/gitea/gitea-docusaurus/pulls/130
• Prepare a new changelog (there are a lot of new changes)
  • Since there are a lot of "backport" PRs in 1.22 milestone like title (#FromPR) (#ThisPR), the changelog should be title (#FromPR), because these PRs now are the real original PR, but not a backport anymore.
• Prepare a release note and explain why, and tell users that 1.22-rc1 and later won't be able to downgrade to 1.22-rc0 (and they shouldn't because many bugs are only fixed in 1.22-rc1) https://gitea.com/gitea/blog/pulls/367
  • "There will be no impact to end users who are using 1.22-rc0, they could safely upgrade to 1.22-rc1 and get more bug fixes and new enhancements"
• Announce and encourage users to test the RC1 release.

[silverwind]

And dont' forget to move the GitHub release out of draft. And I think keep the "Latest" tag on latest v1.21 until stable v1.22 release.

[wxiaoguang]

The PRs for changelog:

prs.json

[wxiaoguang]

Are the formal documents ready? I think it's time to move to next step, for a 1.22.0 release.

[lunny]

Are the formal documents ready? I think it's time to move to next step, for a 1.22.0 release.

https://gitea.com/gitea/blog/pulls/367