From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id aa286597 for ; Mon, 16 Dec 2019 01:22:20 +0000 (UTC) Received: (qmail 10961 invoked by alias); 16 Dec 2019 01:22:14 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 45040 Received: (qmail 24581 invoked by uid 1010); 16 Dec 2019 01:22:14 -0000 X-Qmail-Scanner-Diagnostics: from mail-yb1-f170.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.1/25663. spamassassin: 3.4.2. Clear:RC:0(209.85.219.170):SA:0(-1.9/5.0):. Processed in 2.186678 secs); 16 Dec 2019 01:22:14 -0000 X-Envelope-From: dana@dana.is X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.219.170 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=SlekWiLeqr/rf289z/mxyY7dxtFWfJSq2zD7OugwpCM=; b=qoOapY2ZN+Z653w5fwvYtX1WjAgNiy8+0VuEnQ2iLebhS8lJ3jXkc8f+G4pyPA1N6S bjPoSUtjbhpJkDp1szSUla2eT9ViXEkdmFWg7RB5CUjnNTdhMR2l49pPKZ+8cP8fGaSX zuc/gwKFz/TWX0NpEL9GI+bTduNWC9qdwBUutx8V7CCkRV6ICYMgrpfUiLdv4/LBtWif V/4DO1WNU+ErEoDDRQvwhZsGdel0tHeNM5chPPvtl2vcamreiAY1DqUy/0AWinYjqH6S +lvM8LozfwsGOxijJUKqX5yxdkYR44DN7to7zlqQUEwubbARMHsTQL9+9Vw673xDwSS6 rhIA== X-Gm-Message-State: APjAAAXnNyOrG5T+yQtpksBirLL8h3YWElTBUcq0n2D9OrS5cfsL/RpL FHMBq7IctoK31UUZKTMS5fc8pEECMgk9rw== X-Google-Smtp-Source: APXvYqzq1M6NqdfpqR5jo7nNmRSSieuI1ZRvGwzw0O08zYZuEGkp638wE+2FzJPoIQNM0uKRXvXTtw== X-Received: by 2002:a25:47c2:: with SMTP id u185mr17433207yba.431.1576459298911; Sun, 15 Dec 2019 17:21:38 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Test release: 5.7.1-test-1 From: dana In-Reply-To: <962BC438-3F7D-41E0-A8BD-9300E5DE1DE8@dana.is> Date: Sun, 15 Dec 2019 19:21:37 -0600 Cc: Daniel Shahaf , Peter Stephenson Content-Transfer-Encoding: quoted-printable Message-Id: <853241F8-6C07-4F21-BB1B-C772B53A458F@dana.is> References: <8D05A1CC-D633-4027-9710-0E4D8E56C97C@dana.is> <189cf738-4029-49f3-b502-dc058e11eb63@www.fastmail.com> <20191215051629.ikoezos6bsnirplf@tarpaulin.shahaf.local2> <962BC438-3F7D-41E0-A8BD-9300E5DE1DE8@dana.is> To: Zsh Workers List X-Mailer: Apple Mail (2.3445.104.11) On 15 Dec 2019, at 12:28, Peter Stephenson = wrote: > I've tended to put the final details in release documentation for test > releases so that people can check it before the release. Otherwise = it's > easy to miss something at the last minute, and then it's too late. (Didn't get this in my in-box for some reason) That makes sense to me, personally. And it is a test release for the = next version, after all, not for the previous one (though i can see how the 'stable' bit in the README might be confusing). I've incorporated this = and the incrementing thing into the document below, but obv we can discuss = further if necessary dana diff --git a/Etc/creating-a-release.txt b/Etc/creating-a-release.txt index dfde269ae..059c2aced 100644 --- a/Etc/creating-a-release.txt +++ b/Etc/creating-a-release.txt @@ -6,15 +6,28 @@ To create a zsh release: - Bump or update: =20 Config/version.mk to today's date - Config/version.mk version number (sequence: 5.4.2, = 5.4.2-dev-$((i++)), 5.4.2-test-$((++j)), 5.5) + Config/version.mk version number Etc/FAQ.yo README NEWS =20 + The version-number sequence is as follows: + + 5.6.2, 5.6.2-dev-0, 5.6.2-dev-1, 5.6.2-test-2, 5.6.2-test-3, 5.7 + + (Note the unbroken last-digit sequence going from -dev- to -test-.) + + Usually there is only one -dev- version (-dev-0), but the last digit = may be + incremented if for example there is a wordcode compatibility break, = as in the + real-world example given above. + README should document compatibility-breaking changes. Generally, = NEWS should document new features and major bug fixes (but not routine fixes or = changes to completion/contrib functions). =20 + For -test- releases, you may update the FAQ, README, etc., to refer = to the + appropriate stable version number. + - Commit those changes with an "unposted" ChangeLog entry. =20 git commit -am "Test release: 5.5.1-test-1." && @@ -45,16 +58,21 @@ To create a zsh release: make tarxz-doc tarxz-src for i in zsh*.tar.?z ; do gpg -ab -- $i ; done =20 -- [one time step] Add your key to http://zsh.sf.net/Arc/source.html; = see README in the 'web' repository for how to do this. Its URL is: +- [one time step] Add your key to http://zsh.sf.net/Arc/source.html; = see README + in the 'web' repository for how to do this. Its URL is: =20 git clone git://git.code.sf.net/p/zsh/web git clone ssh://git.code.sf.net/p/zsh/web =20 -- Upload to sf.net +- Upload to sf.net: =20 Test releases go to the "zsh-test" directory. Stable releases to zsh/ and zsh-doc/. - After uploading, select the tar.xz artifact, press the =F0=9F=9B=88= button ("View Details") to its right, and press [Select All] next to = "Default Download For:". This should cause sf.net to offer that = artifact in the "Looking for the latest version?" line. + For stable releases only, after uploading, select the tar.xz = artifact + under zsh/, press the =F0=9F=9B=88 button ("View Details") to = its right, and + press [Select All] next to "Default Download For:". This should = cause + sf.net to offer that artifact in the "Looking for the latest = version?" + line. =20 - If the new release is a stable release, update zsh.sf.net: =20 @@ -94,8 +112,8 @@ To create a zsh release: # several minutes to appear afterwards rsync ... =20 -- Upload the build artefacts to zsh.org/pub; you may need assistance = from - another dev if you don't have access to do this. +- For stable releases, upload the build artefacts to zsh.org/pub; you = may need + assistance from another dev if you don't have access to do this. =20 - Post to -workers@ =20