[Update]: Building a new BuddyPress release - document

[emaralive]

Link to the existing GH Documentation page.

https://github.com/buddypress/buddypress/blob/master/docs/contributor/project/release/build-checklist.md#deploying-to-wporg

What needs to be updated?

The requirement to test a build prior to deployment is a bit obscure, for example:

Important

If it's a major or minor release: control everything went fine.

The text should be more definitive as to the document that is being linked, e.g., something on the lines of:

Important

Prior to deployment to wporg: verfy and validate the build in accordance with Testing a release before deploying it.

Additional tasks to perform:

• Miscellaneous grammatical improvements, a.k.a wordsmithing
• Remove reference(s) to @imath in document (top of document - Note or 2nd paragraph), props to @renatonascalves for providing comment

Handbook of the page to update

buddypress/docs/contributor

Tasks to accomplish

• This task has been added to the "Todo" panel of the Documentation project.
• A PR has been submitted to the BuddyPress GH repository, it has been linked to this issue/task & the task was moved to the "In progress" panel of the Documentation project.
• The PR has been converted to a SVN patch and committed to the BuddyPress SVN repository & the task was moved to the "Done" panel of the Documentation project.

[renatonascalves]

@imath is no longer in Slack, so I think he should be removed from the list of options to ask for support. Or documentation should be added to the proper way to communicate with him.

[emaralive]

@renatonascalves - Got it, at the top of the document the Note or 2nd paragraph is where his handle/mention should be removed. Edited the issue to reflect your comment.

[emaralive]

Other considerations for updates, taken from Docs-chat agenda February 9, 2025 and Slack Archive;

• Assumes svn local repo is set up
• How is the db_version determined for a major release?
• Assumes the node and npm versions match what is specified in package.json
• Should git-svn be an alternative method
• How to handle rate limiting, e.g., svn checkout results in status 429 for some individuals
• Should npm audit fix be used when indicated?
• Is the contact list current?

Additional thought:

• Changes to "Hello, Buddypress!" - What's new? tab - Major build consideration

[renatonascalves]

How is the db_version determined for a major release?

it's my understanding we always need to bump it with major versions.

How to handle rate limiting, e.g., svn checkout results in status 429 for some individuals

As a VPN user, I always have to turn it off to use trac, etc. So I assume WordPress/Automattic might be doing some ip blocking here.

Should npm audit fix be used when indicated?

Not sure what you meant here.

We should also discuss this as part of https://buddypress.trac.wordpress.org/ticket/9080