<pre style='margin:0'>
Lawrence Velázquez (larryv) pushed a commit to branch master
in repository macports-base.
</pre>
<p><a href="https://github.com/macports/macports-base/commit/fcd3f5d3f9cf914df3db04d52d44d60f68d99f48">https://github.com/macports/macports-base/commit/fcd3f5d3f9cf914df3db04d52d44d60f68d99f48</a></p>
<pre style="white-space: pre; background: #F8F8F8"><span style='display:block; white-space:pre;color:#808000;'>commit fcd3f5d3f9cf914df3db04d52d44d60f68d99f48
</span>Author: Lawrence Velázquez <larryv@macports.org>
AuthorDate: Thu Nov 17 21:09:25 2016 -0500
<span style='display:block; white-space:pre;color:#404040;'> ReleaseProcess: Add URLs and fix existing syntax
</span>---
portmgr/ReleaseProcess.md | 94 ++++++++++++++++++++++++++++++-----------------
1 file changed, 61 insertions(+), 33 deletions(-)
<span style='display:block; white-space:pre;color:#808080;'>diff --git a/portmgr/ReleaseProcess.md b/portmgr/ReleaseProcess.md
</span><span style='display:block; white-space:pre;color:#808080;'>index 36d1ece..91624a1 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/portmgr/ReleaseProcess.md
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/portmgr/ReleaseProcess.md
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -50,7 +50,8 @@ be branched for a given release.
</span>
Once master is to be used for development of the next major version, increase
its version information to indicate it's moved past the release version by
<span style='display:block; white-space:pre;background:#ffe0e0;'>-setting the patch-level version to 99, e.g. 2.0.99 in config/macports_version.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+setting the patch-level version to 99, e.g. 2.0.99 in
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[`config/macports_version`][macports_version].
</span>
### Prepare the code for Release ###
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -58,25 +59,27 @@ setting the patch-level version to 99, e.g. 2.0.99 in config/macports_version.
</span> In preparation for a release, several things should be completed within the
code:
<span style='display:block; white-space:pre;background:#ffe0e0;'>-* Update the file ChangeLog in both master and the release branch to reflect
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- the appropriate changes.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* Update the file config/macports_version with the target release number.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- The content of this file is recorded as the MacPorts version at MacPorts
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- build time, as displayed by the port command, and it's also used by the
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- selfupdate procedure to determine whether a newer version of code is
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- available. It should be different between master and the release branch,
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- the former greater to differentiate it from the latter.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* Preserve config/mp_version and config/dp_version at the 1.800 or 1.710
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- fixed values, respectively, if selfupdate backwards compatibility with old
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- MacPorts installations is still desired. (see
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- https://trac.macports.org/changeset/43571/trunk/base or ce8a77c)
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* Update the autoconf 'configure' script through the provided
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- base/autogen.sh script once the version number in `mp_version` has been
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- changed, since the former reads the latter.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* Update the file [`ChangeLog`][ChangeLog] in both master and the release
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ branch to reflect the appropriate changes.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* Update the file [`config/macports_version`][macports_version] with the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ target release number. The content of this file is recorded as the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ MacPorts version at MacPorts build time, as displayed by the port command,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ and it's also used by the selfupdate procedure to determine whether
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ a newer version of code is available. It should be different between
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ master and the release branch, the former greater to differentiate it from
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ the latter.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* Preserve [`config/mp_version`][mp_version] and
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ [`config/dp_version`][dp_version] at the 1.800 or 1.710 fixed values,
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ respectively, if selfupdate backwards compatibility with old MacPorts
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ installations is still desired. (see
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ https://trac.macports.org/changeset/43571/trunk/base or [ce8a77c][])
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* Update the autoconf [`configure`][configure] script through the provided
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ [`autogen.sh`][autogen.sh] script once the version number in `mp_version`
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ has been changed, since the former reads the latter.
</span> * Make sure that these and any other changes or bug fixes are made on and/or
merged between the release branch and master as needed. For instance, if
<span style='display:block; white-space:pre;background:#ffe0e0;'>- you've made changes to ChangeLog only on the release branch, those changes
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- should be merged back into master as well.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ you've made changes to `ChangeLog` only on the release branch, those
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ changes should be merged back into master as well.
</span>
### Tag the Release ###
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -128,7 +131,7 @@ The release should be signed with a detached GPG signature in order to allow
</span> cryptographic verification. To do this automatically, use the additional
argument `DISTGPGID` on the make command. The value specifies a key ID either
in hexadecimal format or a email address matching exactly one key. For
<span style='display:block; white-space:pre;background:#ffe0e0;'>-details, see HOW TO SPECIFY A USER ID in gpg(1) for details.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+details, see [HOW TO SPECIFY A USER ID in gpg(1)][gpg-user-id] for details.
</span>
make dist DISTVER=2.0.0 DISTGPGID=<handle>@macports.org
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -226,10 +229,10 @@ and attach all tarballs and installers to it.
</span> ### Make the Release Available through Self-Update ###
In order to make the release version available through selfupdate, the
<span style='display:block; white-space:pre;background:#ffe0e0;'>-config/RELEASE_URL file in the base repository needs to be updated with the
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-tag of the release to distribute. This file is read by the cron job that makes
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-the code available via rsync. See jobs/mprsyncup in the macports-infra
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-repository.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[`config/RELEASE_URL`][RELEASE_URL] file in the base repository needs to be
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+updated with the tag of the release to distribute. This file is read by the
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+cron job that makes the code available via rsync. See
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[`jobs/mprsyncup`][mprsyncup] in the macports-infra repository.
</span>
### Notify the Public of the Release ###
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -237,22 +240,24 @@ repository.
</span> Once the release has been posted, notification of the release should be
sent/posted to the following places:
<span style='display:block; white-space:pre;background:#ffe0e0;'>-* The macports-announce@, macports-users@ and macports-dev@ mailing lists.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* The [macports-announce][]@, [macports-users][]@ and [macports-dev][]@
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ mailing lists.
</span> * The MacPorts website, by adapting the `$macports_version_major` and
`$macports_version_latest` variables as appropriate in the
<span style='display:block; white-space:pre;background:#ffe0e0;'>- includes/common.inc file in the macports-www repository.
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* The website's news section at https://macports.github.io/news/, see the
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- macports.github.io repository
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-* The `&macports-version;` entity in xml/installing.xml and xml/using.xml in
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>- the guide repository.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ [`includes/common.inc`][common.inc] file in the macports-www repository.
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* The [news section][news] of the website (see the [macports.github.io][]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ repository)
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+* The `&macports-version;` entity in
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ [`guide/xml/installing.xml`][installing.xml] and
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ [`guide/xml/using.xml`][using.xml] in the guide repository.
</span> * External websites
<span style='display:block; white-space:pre;background:#ffe0e0;'>- * [http://sourceforge.net/projects/macports/ sourceforge]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ * [SourceForge][]
</span> (submitter: portmgr@)
<span style='display:block; white-space:pre;background:#ffe0e0;'>- * [https://www.macupdate.com/app/mac/21309/macports MacUpdate]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ * [MacUpdate][]
</span> (submitter: ???)
<span style='display:block; white-space:pre;background:#ffe0e0;'>- * [http://twitter.com/macports twitter]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ * [Twitter][]
</span> (submitter: raimue@)
<span style='display:block; white-space:pre;background:#ffe0e0;'>- * [https://plus.google.com/communities/110287630398071712872 Google+ Community]
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+ * [Google+ Community][Google+]
</span> (submitter: raimue@)
* (Where else?)
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -265,4 +270,27 @@ installations to the new release. This delay matches the warning about
</span> outdated ports tree sources.
<span style='display:block; white-space:pre;background:#e0ffe0;'>+[autogen.sh]: /autogen.sh
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[ce8a77c]: https://github.com/macports/macports-base/commit/ce8a77c858c679f2d7627a3cd613436b2ead82e7
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[ChangeLog]: /ChangeLog
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[common.inc]: https://github.com/macports/macports-www/blob/master/includes/common.inc
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[configure]: /configure
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[dp_version]: /config/dp_version
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[Google+]: https://plus.google.com/communities/110287630398071712872
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[gpg-user-id]: https://gnupg.org/documentation/manuals/gnupg/Specify-a-User-ID.html
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[installing.xml]: https://github.com/macports/macports-guide/blob/master/guide/xml/installing.xml
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[macports-announce]: mailto:macports-announce@lists.macports.org
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[macports-dev]: mailto:macports-dev@lists.macports.org
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[macports-users]: mailto:macports-users@lists.macports.org
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[macports.github.io]: https://github.com/macports/macports.github.io
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[macports_version]: /config/macports_version
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[MacUpdate]: https://www.macupdate.com/app/mac/21309/macports
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[mp_version]: /config/mp_version
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[mprsyncup]: https://github.com/macports/macports-infrastructure/blob/master/jobs/mprsyncup
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[news]: https://www.macports.org/news
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[RELEASE_URL]: /config/RELEASE_URL
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[SourceForge]: http://sourceforge.net/projects/macports
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[Twitter]: http://twitter.com/macports
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+[using.xml]: https://github.com/macports/macports-guide/blob/master/guide/xml/using.xml
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+
</span> <!-- vim:set fenc=utf-8 ft=markdown tw=78 et sw=4 sts=4: -->
</pre><pre style='margin:0'>
</pre>