guile-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Guile-commits] 01/02: Update release.org


From: Andy Wingo
Subject: [Guile-commits] 01/02: Update release.org
Date: Wed, 15 Jan 2020 15:24:38 -0500 (EST)

wingo pushed a commit to branch master
in repository guile.

commit 20219f403714941d0454622d7fc881e1bdacb679
Author: Andy Wingo <address@hidden>
AuthorDate: Wed Jan 15 21:15:47 2020 +0100

    Update release.org
    
    * doc/release.org: Update for 3.0
---
 doc/release.org | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/doc/release.org b/doc/release.org
index 2712866..eaa513f 100644
--- a/doc/release.org
+++ b/doc/release.org
@@ -1,9 +1,9 @@
-#+TITLE: Release Process for GNU Guile 2.2
+#+TITLE: Release Process for GNU Guile 3.0
 #+AUTHOR: Ludovic Court├Ęs
 #+STARTUP: content
 #+EMAIL: address@hidden
 
-This document describes the typical release process for Guile 2.2.
+This document describes the typical release process for Guile 3.0.
 
 * Preparing & uploading the tarball
 
@@ -69,16 +69,16 @@ if in doubt.
 
 `libguile/libguile.map' should also be updated as new public symbols are
 added.  Ideally, new symbols should get under a new version
-symbol---e.g., `GUILE_2.2.3' for symbols introduced in Guile 2.2.3.
+symbol---e.g., `GUILE_3.0.3' for symbols introduced in Guile 3.0.3.
 
-** Tag v2.2.x
+** Tag v3.0.x
 
 Create a signed Git tag, like this:
 
-  $ git tag -s -u MY-KEY -m "GNU Guile 2.2.X." v2.2.X
+  $ git tag -s -u MY-KEY -m "GNU Guile 3.0.X." v3.0.X
 
-The tag *must* be `v2.2.X'.  For the sake of consistency, always use
-"GNU Guile 2.2.X." as the tag comment.
+The tag *must* be `v3.0.X'.  For the sake of consistency, always use
+"GNU Guile 3.0.X." as the tag comment.
 
 ** Push the tag and changes
 
@@ -97,7 +97,7 @@ reports the new version number.
 
 ** Upload
 
-  $ ./build-aux/gnupload --to ftp.gnu.org:guile guile-2.2.X.tar.gz
+  $ ./build-aux/gnupload --to ftp.gnu.org:guile guile-3.0.X.tar.{lz,xz,gz}
 
 You'll get an email soon after when the upload is complete.
 
@@ -114,10 +114,10 @@ Make sure the file was uploaded and is available for 
download as
 expected:
 
   $ mkdir t && cd t && \
-    wget ftp.gnu.org/gnu/guile/guile-2.2.X.tar.gz && \
-    wget ftp.gnu.org/gnu/guile/guile-2.2.X.tar.xz
-  $ diff guile-2.2.X.tar.gz ../guile-2.2.X.tar.gz
-  $ diff guile-2.2.X.tar.xz ../guile-2.2.X.tar.xz
+    wget ftp.gnu.org/gnu/guile/guile-3.0.X.tar.gz && \
+    wget ftp.gnu.org/gnu/guile/guile-3.0.X.tar.xz
+  $ diff guile-3.0.X.tar.gz ../guile-3.0.X.tar.gz
+  $ diff guile-3.0.X.tar.xz ../guile-3.0.X.tar.xz
 
 You're almost done!
 
@@ -139,17 +139,17 @@ Announcements").
 Use `build-aux/gendocs', add to the manual/ directory of the web site.
 
   $ cd doc/ref
-  $ ../../build-aux/gendocs.sh guile "GNU Guile 2.2.X Reference Manual"
+  $ ../../build-aux/gendocs.sh guile "GNU Guile 3.0.X Reference Manual"
 
 ** Prepare the email announcement
 
   $ build-aux/announce-gen --release-type=stable --package-name=guile \
-      --previous-version=2.2.1 --current-version=2.2.2 \
+      --previous-version=3.0.1 --current-version=3.0.2 \
       --gpg-key-id=MY-KEY --url-directory=ftp://ftp.gnu.org/gnu/guile \
       --bootstrap-tools=autoconf,automake,libtool,gnulib,makeinfo \
       --gnulib-version=$( cd ~/src/gnulib ; git describe )
 
-The subject must be "GNU Guile 2.2.X released".  The text should remain
+The subject must be "GNU Guile 3.0.X released".  The text should remain
 formal and impersonal (it is sent on behalf of the Guile and GNU
 projects.)  It must include a description of what Guile is (not everyone
 reading info-gnu may know about it.)  Use the text of previous



reply via email to

[Prev in Thread] Current Thread [Next in Thread]