svn commit: r1305351 - /subversion/site/publish/docs/community-guide/releasing.part.html

[st...@apache.org]

Author: stsp
Date: Mon Mar 26 13:35:32 2012
New Revision: 1305351

URL: http://svn.apache.org/viewvc?rev=1305351&view=rev
Log:
* publish/docs/community-guide/releasing.part.html: Explain how to roll a -deps
   tarball for 1.6.x releases.

Modified:
    subversion/site/publish/docs/community-guide/releasing.part.html

Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=1305351&r1=1305350&r2=1305351&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Mon Mar 26 13:35:32 2012
@@ -719,6 +719,16 @@ PATH="/opt/svnrm/bin:$PATH" ./release.py
 </pre>
 When release.py is done you'll have tarballs within the
 <tt>/opt/svnrm/deploy</tt> directory.</p> 
+
+<p>For 1.6.x releases, a -deps tarball must be created that contains the
+set of default dependencies. Use the <a
+href="https://svn.apache.org/repos/asf/subversion/trunk/tools/dist/make-deps-tarball.sh"
+>make-release-tarball.sh</a> script to create it. Before creating the
+-deps tarballs, check if newer stable releases of the dependencies exist,
+and adjust version numbers in the script if necessary. Please be conservative
+when upgrading the default dependencies for 1.6.x. We want the -deps tarball
+to contain bug fixes that were made since the last Subversion-1.6.x release
+but avoid upgrading dependencies to new release lines that add new features.</p>
  
 <p>Test one or both of the tarballs:</p>