<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>[BuddyPress][14122] trunk/docs/contributor/project/release/build-checklist.md: Update build-checklist.md</title>
</head>
<body>
<style type="text/css"><!--
#msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px; color: #fff; }
#msg dl.meta dt { float: left; width: 6em; font-weight: bold; }
#msg dt:after { content:':';}
#msg dl, #msg dt, #msg ul, #msg li, #header, #footer, #logmsg { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; }
#msg dl a { font-weight: bold}
#msg dl a:link { color:#fc3; }
#msg dl a:active { color:#ff0; }
#msg dl a:visited { color:#cc6; }
h3 { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; font-weight: bold; }
#msg pre { white-space: pre-line; overflow: auto; background: #ffc; border: 1px #fa0 solid; padding: 6px; }
#logmsg { background: #ffc; border: 1px #fa0 solid; padding: 1em 1em 0 1em; }
#logmsg p, #logmsg pre, #logmsg blockquote { margin: 0 0 1em 0; }
#logmsg p, #logmsg li, #logmsg dt, #logmsg dd { line-height: 14pt; }
#logmsg h1, #logmsg h2, #logmsg h3, #logmsg h4, #logmsg h5, #logmsg h6 { margin: .5em 0; }
#logmsg h1:first-child, #logmsg h2:first-child, #logmsg h3:first-child, #logmsg h4:first-child, #logmsg h5:first-child, #logmsg h6:first-child { margin-top: 0; }
#logmsg ul, #logmsg ol { padding: 0; list-style-position: inside; margin: 0 0 0 1em; }
#logmsg ul { text-indent: -1em; padding-left: 1em; }#logmsg ol { text-indent: -1.5em; padding-left: 1.5em; }
#logmsg > ul, #logmsg > ol { margin: 0 0 1em 0; }
#logmsg pre { background: #eee; padding: 1em; }
#logmsg blockquote { border: 1px solid #fa0; border-left-width: 10px; padding: 1em 1em 0 1em; background: white;}
#logmsg dl { margin: 0; }
#logmsg dt { font-weight: bold; }
#logmsg dd { margin: 0; padding: 0 0 0.5em 0; }
#logmsg dd:before { content:'\00bb';}
#logmsg table { border-spacing: 0px; border-collapse: collapse; border-top: 4px solid #fa0; border-bottom: 1px solid #fa0; background: #fff; }
#logmsg table th { text-align: left; font-weight: normal; padding: 0.2em 0.5em; border-top: 1px dotted #fa0; }
#logmsg table td { text-align: right; border-top: 1px dotted #fa0; padding: 0.2em 0.5em; }
#logmsg table thead th { text-align: center; border-bottom: 1px solid #fa0; }
#logmsg table th.Corner { text-align: left; }
#logmsg hr { border: none 0; border-top: 2px dashed #fa0; height: 1px; }
#header, #footer { color: #fff; background: #636; border: 1px #300 solid; padding: 6px; }
#patch { width: 100%; }
#patch h4 {font-family: verdana,arial,helvetica,sans-serif;font-size:10pt;padding:8px;background:#369;color:#fff;margin:0;}
#patch .propset h4, #patch .binary h4 {margin:0;}
#patch pre {padding:0;line-height:1.2em;margin:0;}
#patch .diff {width:100%;background:#eee;padding: 0 0 10px 0;overflow:auto;}
#patch .propset .diff, #patch .binary .diff {padding:10px 0;}
#patch span {display:block;padding:0 10px;}
#patch .modfile, #patch .addfile, #patch .delfile, #patch .propset, #patch .binary, #patch .copfile {border:1px solid #ccc;margin:10px 0;}
#patch ins {background:#dfd;text-decoration:none;display:block;padding:0 10px;}
#patch del {background:#fdd;text-decoration:none;display:block;padding:0 10px;}
#patch .lines, .info {color:#888;background:#fff;}
--></style>
<div id="msg">
<dl class="meta" style="font-size: 105%">
<dt style="float: left; width: 6em; font-weight: bold">Revision</dt> <dd><a style="font-weight: bold" href="http://buddypress.trac.wordpress.org/changeset/14122">14122</a><script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","description":"Review this Commit","action":{"@type":"ViewAction","url":"http://buddypress.trac.wordpress.org/changeset/14122","name":"Review Commit"}}</script></dd>
<dt style="float: left; width: 6em; font-weight: bold">Author</dt> <dd>dcavins</dd>
<dt style="float: left; width: 6em; font-weight: bold">Date</dt> <dd>2025-03-21 02:29:53 +0000 (Fri, 21 Mar 2025)</dd>
</dl>
<pre style='padding-left: 1em; margin: 2em 0; border-left: 2px solid #ccc; line-height: 1.25; font-size: 105%; font-family: sans-serif'>Update build-checklist.md
Add notes about how to build a release for a previous version.</pre>
<h3>Modified Paths</h3>
<ul>
<li><a href="#trunkdocscontributorprojectreleasebuildchecklistmd">trunk/docs/contributor/project/release/build-checklist.md</a></li>
</ul>
</div>
<div id="patch">
<h3>Diff</h3>
<a id="trunkdocscontributorprojectreleasebuildchecklistmd"></a>
<div class="modfile"><h4 style="background-color: #eee; color: inherit; margin: 1em 0; padding: 1.3em; font-size: 115%">Modified: trunk/docs/contributor/project/release/build-checklist.md</h4>
<pre class="diff"><span>
<span class="info" style="display: block; padding: 0 10px; color: #888">--- trunk/docs/contributor/project/release/build-checklist.md 2025-03-20 20:25:42 UTC (rev 14121)
+++ trunk/docs/contributor/project/release/build-checklist.md 2025-03-21 02:29:53 UTC (rev 14122)
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -2,7 +2,7 @@
</span><span class="cx" style="display: block; padding: 0 10px">
</span><span class="cx" style="display: block; padding: 0 10px"> Releasing BuddyPress to the world is a big deal, and takes quite a few manual steps to ensure safe & comfortable updates & upgrades are had by all. Below are the steps release leads go through with each & every release.
</span><span class="cx" style="display: block; padding: 0 10px">
</span><del style="background-color: #fdd; text-decoration:none; display:block; padding: 0 10px">-Note: These steps vary slightly depending on major/minor/urgency of the deployment to WordPress.org. For questions, or if something is not clear, please ping [@JJJ](https://profiles.wordpress.org/johnjamesjacoby), [@boone](https://profiles.wordpress.org/boonebgorges/), [@djpaul](https://profiles.wordpress.org/djpaul/) or [@imath](https://profiles.wordpress.org/imath/) on [Slack](https://wordpress.slack.com/messages/buddypress). They are mad enough to comprehend how & why all this works the way it does. (We keep planning to automate this, but until then, please enjoy this extremely long and intimidating list of responsibilities.)
</del><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+Note: These steps vary slightly depending on major/minor/urgency of the deployment to WordPress.org. For questions, or if something is not clear, please ping [@JJJ](https://profiles.wordpress.org/johnjamesjacoby), [@boone](https://profiles.wordpress.org/boonebgorges/) or [@djpaul](https://profiles.wordpress.org/djpaul/) on [Slack](https://wordpress.slack.com/messages/buddypress). They are mad enough to comprehend how & why all this works the way it does. (We keep planning to automate this, but until then, please enjoy this extremely long and intimidating list of responsibilities.)
</ins><span class="cx" style="display: block; padding: 0 10px">
</span><span class="cx" style="display: block; padding: 0 10px"> ## Prologue
</span><span class="cx" style="display: block; padding: 0 10px"> There are two code repositories, and you’ll be tasked with compiling the BuddyPress codebase from the development repo to the deployment repo. They are separate because BuddyPress is deployed to almost all end-users from the public WordPress.org plugin repository in a way that requires some development assets to be pre-compiled (it’s not a literal 1-to-1 copy) and because BuddyPress is lucky enough to have its own Trac instance on WordPress.org.
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -107,6 +107,8 @@
</span><span class="cx" style="display: block; padding: 0 10px"> > [!IMPORTANT]
</span><span class="cx" style="display: block; padding: 0 10px"> > If it's a major or minor release: [control everything went fine](./test-checklist.md).
</span><span class="cx" style="display: block; padding: 0 10px">
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+**If you are updating the "current" version**:
+
</ins><span class="cx" style="display: block; padding: 0 10px"> + If lights are green, overwrite the contents of the trunk directory with the contents of `build` in the [wporg] checkout.
</span><span class="cx" style="display: block; padding: 0 10px"> + If it’s a beta or a release candidate, make sure the Stable tag in both trunk and the newly created tag are the same and are the one of current stable version of BuddyPress.
</span><span class="cx" style="display: block; padding: 0 10px"> + Run `svn stat` to check if you need to`svn add` or `svn delete` files.
</span><span class="lines" style="display: block; padding: 0 10px; color: #888">@@ -118,6 +120,19 @@
</span><span class="cx" style="display: block; padding: 0 10px"> svn ci -m 'Update trunk with X.Y.Z code & create X.Y.Z tag from trunk'
</span><span class="cx" style="display: block; padding: 0 10px"> ```
</span><span class="cx" style="display: block; padding: 0 10px">
</span><ins style="background-color: #dfd; text-decoration:none; display:block; padding: 0 10px">+**If you are updating a previous version** (backporting security fixes for instance):
+
++ Ensure that there is a branch ready to use for the version you are releasing. **If you need to create a branch that doesn't exist**, search the SVN log for the revision that created the newest release of that version. You can search like this, for instance: `svn log --search 12.5`. With the revision number found in the log search, you can create a new branch from the state of `trunk` at that release, like this: `svn cp -r3259416 trunk branches/12.0`.
++ If lights are green, overwrite the contents of the branch directory for the version you are building (like `branches/12.0`) with the contents of `build` in the [wporg] checkout.
++ Run `svn stat` to check if you need to`svn add` or `svn delete` files.
++ Create an svn tag from the branch you updated above using a command like `svn cp branches/12 tags/12.5.0`.
++ Make sure the Stable tag in `readme.txt` in `trunk` still matches the "current" version, not the older version you are fixing.
++ Commit & 🤞!
+
+```bash
+svn ci -m 'Update branches/12.0 with 12.5.3 code & create 12.5.3 tag from branches/12.0'
+```
+
</ins><span class="cx" style="display: block; padding: 0 10px"> > [!IMPORTANT]
</span><span class="cx" style="display: block; padding: 0 10px"> > If it's a major or minor release: Control everything went fine.
</span><span class="cx" style="display: block; padding: 0 10px">
</span></span></pre>
</div>
</div>
</body>
</html>