Here's an even simpler fix to enable TLS by default.

[nmh] / docs / README.developers

diff --git a/docs/README.developers b/docs/README.developers
index 8b9ecdf0ece3f4ad7e7511f6bec37fef4b551c1e..ec0b29d7308528d4c791becc8fbf77e10f04d872 100644 (file)
--- a/docs/README.developers
+++ b/docs/README.developers
@@ -216,11 +216,18 @@ here; the convention for release candidates is to use something like
 
     % git branch 1.5-release
 
 
     % git branch 1.5-release
 

-    Note you are still on the master branch at this point.  So mark that
-    master will now be post-1.5:
+    Note you are still on the master branch at this point.  Mark the
+    current revision as the branchpoint for the new release branch:
+    
+    % git tag -a -m "This tag marks the point where we started the branch for 1.5" 1.5-branchpoint
+
+    Now mark the master branch with a post-release version number (the
+    convention here is to use VERSION+dev as the version number).

 
     % echo 1.5+dev > VERSION
 
     % echo 1.5+dev > VERSION

-    % git commit VERSION; git push
+    % git commit VERSION
+    % git push
+    % git push --tags

 
     Then do:
 
 
     Then do:
 


@@ -235,6 +242,7 @@ here; the convention for release candidates is to use something like
  3. % git commit VERSION DATE; git push
 
  4. % git tag -a 1.5 -m 'Releasing nmh-1.5.'
  3. % git commit VERSION DATE; git push
 
  4. % git tag -a 1.5 -m 'Releasing nmh-1.5.'

+    % git push --tags

 
     Note that the new convention for tagging is to simply tag with the
     version number (tag formats in the past have varied).
 
     Note that the new convention for tagging is to simply tag with the
     version number (tag formats in the past have varied).