<p>I am going to ask you some questions which will allow you to quickly make the decisions needed to get the whole release out without any additional thought. If you don\'t like these questions (such as finding them personally intrusive), I don\'t care… I am merely a machine, a device, working against a precomputed script. Now that is out of the way…</p>
<hr />
<fieldset>
<legend>OLD version number</legend>
<label for="version">The old version number was detected below from git (or blank if I could not determine it). The auto-generated changelog on the next page will contain resolved tracker issues and git commits since this version.</label>
<label for="version">What is the full version number (no bloody A, B, C, or D) of the NEW version you are releasing right now? If you are only testing the make release process, you should leave this value alone (use the on-disk version).</label>
<p>Here are some things you should do if you have not already:</p>
<ul>
<li>Go through the auto-reported error emails, to make sure they are handled (for each: fix if relevant, delete if not).</li>
<li>Run the <a href="'.escape_html(get_base_url().'/_tests').'">unit tests</a><!--, with dev mode on, on the custom Composr PHP version-->.</li>
<li>Edit sources/version.php to reflect the new version being released (and refresh this page so the pre-defined fields below represent the new version).</li>
<p>I am going to ask you some questions which will allow you to quickly make the decisions needed to get the whole release out without any additional thought. If you don\'t like these questions (such as finding them personally intrusive), I don\'t care… I am merely a machine, a device, working against a precomputed script. Now that is out of the way…</p>
<p>Now that I know the new and previous version, I have generated a changelog for you (because work smarter, not harder). Please review it carefully.</p>
<hr />
<fieldset>
<legend>Version number</legend>
<label for="version">What is the full version number (no bloody A, B, C, or D)?</label>
<label for="changes">For a patch release the default is usually fine (links to our hotfixes and git history). A list of changes is rarely of much use and takes many hours to put together. Users should just stay updated regardless, and will know if there is some specific hotfix that was already made available to them. For a major release much more consideration is needed.</label>
<label for="changes">For a patch release the default is usually fine (links to our hotfixes and git history). A list of changes takes many hours to put together. Users should just stay updated regardless, and will know if there is some specific hotfix that was already made available to them. For a major release much more consideration is needed.</label>
<strong>Upload</strong>: Upload all built files (in <a href="#" onclick="fauxmodal_alert(\'<kbd>'.escape_html($command_to_try).'</kbd>\',null,\'Command to open folder\',true);"><kbd>exports/builds/'.escape_html($version_dotted).'</kbd></a>) to compo.sr server (<a target="_blank" href="sftp://web1@compo.sr/composr/uploads/downloads"><kbd>uploads/downloads</kbd></a>)
<strong>Upload</strong>: Upload all built files (in <a href="#" onclick="fauxmodal_alert(\'<kbd>'.escape_html($command_to_try).'</kbd>\',null,\'Command to open folder\',true);"><kbd>exports/builds/'.escape_html($new_version).'</kbd></a>) to compo.sr server (<a target="_blank" href="sftp://web1@compo.sr/composr/uploads/downloads"><kbd>uploads/downloads</kbd></a>)
</li>
<li>
Tag the release with <kbd>git commit -a -m "New build"; git push; git tag '.escape_html($version_dotted).' ; git push origin '.escape_html($version_dotted).'</kbd>
Tag the release with <kbd>git commit -a -m "New build"; git push; git tag '.escape_html($new_version).' ; git push origin '.escape_html($new_version).'</kbd>
</li>
<li>
<strong>Add to compo.sr</strong>: Run the <form target="_blank" style="display: inline" action="'.escape_html($push_url).'" method="post">'.static_evaluate_tempcode(symbol_tempcode('INSERT_SPAMMER_BLACKHOLE')).'<input type="hidden" name="changes" value="'.escape_html($changes).'" /><input class="hyperlink_button" type="submit" value="compo.sr setup script" /></form>. Note if you are re-releasing, this will still work – it will update existing entries appropriately.