Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document release process #1

Open
wants to merge 14 commits into
base: main
Choose a base branch
from
Open

Document release process #1

wants to merge 14 commits into from

Conversation

Jackenmen
Copy link
Member

@Jackenmen Jackenmen commented Jul 7, 2021

@Jackenmen Jackenmen force-pushed the add/release-process branch 3 times, most recently from c8b64cd to ae4e742 Compare July 8, 2021 22:53
@Jackenmen Jackenmen force-pushed the add/release-process branch from ae4e742 to 20ee08d Compare July 8, 2021 23:09
@Jackenmen Jackenmen marked this pull request as ready for review July 9, 2021 18:31
@Jackenmen Jackenmen force-pushed the add/release-process branch from 1d2c26f to b5c413c Compare July 12, 2021 00:18
@Jackenmen Jackenmen force-pushed the add/release-process branch from b5c413c to ec2d270 Compare July 17, 2021 00:32
@Jackenmen
Copy link
Member Author

Jackenmen commented Jul 17, 2021

The descriptions should be correct enough here.

There are still some improvements to be made here though:

  • add some screenshots to step 9 (environment run)
  • step 3 is missing a bit of information on where the changelog PR should be merged
    • it should be merged into V3/develop, backported into 3.x if that's the branch you make a release from, cherry-picked into the short-lived branch in step 6
  • it might be worth converting the stuff done by my RedHelper cog to a simple Python script so that we don't depend on my bot running
    • on the bright side, the getcontributors and getunreleasedcommits commands are available to be run by everyone, not just the bot owner
    • getunreleasedcommits does not work well with 3.x branch as it checks against V3/develop
  • more information on milestone management might be needed, especially with the regular and backport PRs being separate (cherry-pick bot is not yet done so that's also a bit of an issue :))

monjie110

This comment was marked as spam.

monjie110

This comment was marked as spam.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants