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 the release process #594

Merged
merged 1 commit into from
Apr 25, 2024
Merged

Document the release process #594

merged 1 commit into from
Apr 25, 2024

Conversation

vcanales
Copy link
Member

@vcanales vcanales commented Apr 25, 2024

Adds a description of the release process.

Tasks:

  • Provide clarity on who is actually able to review and merge.
  • Warn against closing release PRs without merging.

@vcanales vcanales added the documentation Improvements or additions to documentation label Apr 25, 2024
@vcanales vcanales requested a review from mikachan April 25, 2024 14:34
@pbking
Copy link
Contributor

pbking commented Apr 25, 2024

Use the git cherry-pick [commit-hash] command to add specific commits to the Release Branch associated with the Release PR.

Does the changelog continue to get updated or does that need to happen manually with cherry-picked branches?


### 3 - Finalize the Release

Once the release is deemed complete and ready, it must be reviewed and approved by members of the organization. Following approval, the Release PR is merged into the main branch. This action triggers the [**Deploy to Dotorg**](https://github.com/WordPress/create-block-theme/actions/workflows/deploy-to-dotorg.yml) workflow, which tags the release on both GitHub and the WordPress Plugin Directory SVN. A Release Confirmation is then triggered on WordPress.org, notifying plugin maintainers via email of the new release awaiting confirmation. Upon confirmation, the new version becomes live on the WordPress Plugin Directory.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does github display the members in this list?

@vcanales
Copy link
Member Author

Use the git cherry-pick [commit-hash] command to add specific commits to the Release Branch associated with the Release PR.

Does the changelog continue to get updated or does that need to happen manually with cherry-picked branches?

Good point, I'll need to add a step that automatically updates the Change Log after new commits are added.

Copy link
Contributor

@pbking pbking left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A good change for now. Mentioned cherry-picked changes after creation which will need a follow up.

🚢

@pbking pbking merged commit 9af5497 into trunk Apr 25, 2024
2 checks passed
@pbking pbking deleted the docs/add-release-process-docs branch April 25, 2024 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants