[43572] trunk/base/portmgr/ReleaseProcess

jmpp at macports.org jmpp at macports.org
Thu Dec 11 19:12:55 PST 2008


Revision: 43572
          http://trac.macports.org/changeset/43572
Author:   jmpp at macports.org
Date:     2008-12-11 19:12:55 -0800 (Thu, 11 Dec 2008)
Log Message:
-----------

Briefly document r43571 in the base/portmgr/ReleaseProcess file for quick reference.

Modified Paths:
--------------
    trunk/base/portmgr/ReleaseProcess

Modified: trunk/base/portmgr/ReleaseProcess
===================================================================
--- trunk/base/portmgr/ReleaseProcess	2008-12-12 03:11:11 UTC (rev 43571)
+++ trunk/base/portmgr/ReleaseProcess	2008-12-12 03:12:55 UTC (rev 43572)
@@ -66,10 +66,13 @@
 In preparation for a release, several things should be completed within the code:
 
  * Update the file base/ChangeLog in both trunk and the release branch to reflect the appropriate changes.
- * Update the file base/config/macports_version with the target release number.  The version number in
-   macports_version is displayed by the port command as the version of MacPorts, and is used by the selfupdate
-   command to determine whether a newer version of code is available. This number should be different
-   between trunk and a release branch, the former greater to differentiate it from the latter.
+ * Update the file base/config/macports_version with the target release number. The content of this file
+   is recorded as the MacPorts version at MacPorts build time, as displayed by the port command, and it's
+   also used by the selfupdate procedure to determine whether a newer version of code is available.
+   It should be different between trunk and the release branch, the former greater to differentiate it from
+   the latter.
+ * Preserve the file base/config/mp_version at the 1.800 fixed value if selfupdate backwards compatibility
+   with pre 1.8.0 MacPorts installations is still desired (cf. svn's r43571).
  * Update the autoconf 'configure' script through the provided base/regen.sh script once the version number
    in mp_version has been changed, since the former reads the latter.
  * Make sure that these and any other changes or bug fixes are made on and/or merged between the release branch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-changes/attachments/20081211/fb4e9920/attachment.html>


More information about the macports-changes mailing list