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.

Sign up for GitHub

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

Jump to bottom

RC automatization: overview #15416

Open
1 of 20 tasks
moorscode opened this issue Jun 12, 2020 · 0 comments
Open
1 of 20 tasks

RC automatization: overview #15416

moorscode opened this issue Jun 12, 2020 · 0 comments
Labels
type: development

Comments

@moorscode
Copy link
Contributor

moorscode commented Jun 12, 2020 •
edited
Loading

What needs to be done to have full Release Candidate automation.

Check happy-path:

  • Run through a complete RC cycle
    • See a fail on a non-clean branch
    • Have an RC branch being created or pulled from the remote
    • Make sure the JavaScript packages are up to date
    • Add/update entries for the readme
    • Check the RC version being bumped
    • Sync Gutenberg version
    • Check Github pre-release
    • See the slack notification
    • See trunk on WordPress plugin SVN being updated
    • See the zip-size warning being displayed and issue being made if size > 5MB
    • See if the release branch is merged back into trunk
    • Celebrate a successful Release Candidate

Un-happy-paths:

  • JavaScript packages don't have an RC version for the latest release
  • Create RC script was interrupted, continue without bumping the RC version

Yoast SEO Premium:

  • Create flow for Yoast SEO Premium

Optional tasks:

  • Unify the use of grunt-git vs shell commands
  • Move tasks to the plugin-grunt-tasks repository
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: development
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@moorscode