Follow Release Process for `3.0.0-alpha.2`

[da2ce7]

from: release_process.md

Comments in the Develop Branch:

• The develop branch has the 3.0.0-alpha.2-develop.
• The version is bumped according to releases, new features, and breaking changes.

Process:

• [x] The develop branch is ready for a release.
• [x] Stage develop HEAD for merging into the main branch.
• [x] Create Release Commit: release: version 3.0.0-alpha.2, that removes the -develop suffix.
• [x] Create "Release Version 3.0.0-alpha.2" pull request from from staging/main into main branch.
• [x] Merge "Release Version 3.0.0-alpha.2" pull request.
• [x] Push New Version from main HEAD to releases/v3.0.0-alpha.2 branch.
• [x] Check that the deployment is successful!
• [x] Create Release Tag v3.0.0-alpha.2.
• [x] Create Release on Github from Tag.
• [x] Stage main HEAD for merging into the develop branch.
• [x] Create Comment that bumps next development version.
• [x] Create "Version 3.0.0-alpha.2 was Released" pull request from from staging/develop into develop branch.
• [x] Merge "Version 3.0.0-alpha.2 was Released" pull request.

[josecelano]

It has already been published: https://crates.io/crates/torrust-index-backend/2.0.0-alpha.2

[da2ce7]

@josecelano It was published under the 2.x.x numbering, instead of the 3.x.x numbers.

[josecelano]

@josecelano It was published under the 2.x.x numbering, instead of the 3.x.x numbers.

OK. I always get confused because I tend to think about the next major version for each repo. For this repo it would be v2.0.0, but I forget that you want to use the v3.0.0 for all repos (tracker, index and index GUI).

[da2ce7]

Yeah, the idea was that we bump all the repositories to the same major version to signify that the group release are related.

[josecelano]

It was published by @da2ce7 https://crates.io/crates/torrust-index/3.0.0-alpha.2