mirror of
https://github.com/buddypress/buddypress.git
synced 2026-07-24 21:16:56 +08:00
Closes https://github.com/buddypress/buddypress/pull/373 git-svn-id: https://buddypress.svn.wordpress.org/trunk@14021 cdf35c40-ae34-48e0-9cc9-0c9da1808c22
1.5 KiB
1.5 KiB
Testing a release before deploying it
The minor of major version package has been built, before deploying it to [wp-org] repository, let's control everything went fine testing the build:
- Copy the content of the
buddypress-to-deploy/buildfolder into a newbuddypressfolder. - Zip it.
- Test it on a "fresh" WordPress regular site and then on a WordPress mulisite network.
Tip
If you organized a release party on BuddyPress Slack's channel, don't hesitate to ask other contributors to help you test this new version.
WordPress regular site
- Make sure it's a WordPress fresh install (BuddyPress has not been installed/activated on the site).
- Go to
WP Admin > Plugins > Add newto upload the Zip you created earlier and activate BuddyPress. - Test activating / deactivating all components is happening without issues/notices.
- Add a new WordPress post and then a BP Member block to the post content to check the BP REST API is available via the block's Autocomplete field.
- Switch to BP Nouveau & BP Legacy template packs from
WP Admin > Settings > BuddyPress > Optionsthen go tosite.url/membersto check there are no issues/notices.
WordPress multisite network
- Go to
WP Network Admin > Pluginsto check a previous BuddyPress version is active at the network level. - Go to
WP Network Admin > Plugins > Add newto upload the Zip you created earlier to replace the previous BuddyPress version and simulate a plugin upgrade. - Repeat WP regular site's checklist points 3 to 5.