Skip to content

Release: Publish Gitea 1.22 #30731

Closed
Closed
@lunny

Description

@lunny

1.22.0

Release 1.22.0 in one week if rc1 is stable enough.

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
    • 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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions