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 f6079175 for ; Mon, 16 Dec 2019 22:11:55 +0000 (UTC) Received: (qmail 29513 invoked by alias); 16 Dec 2019 22:11:49 -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: 45056 Received: (qmail 13230 invoked by uid 1010); 16 Dec 2019 22:11:49 -0000 X-Qmail-Scanner-Diagnostics: from mail-yb1-f196.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.196):SA:0(-1.9/5.0):. Processed in 1.469311 secs); 16 Dec 2019 22:11:49 -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.196 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=D6uR/pkU3nP5Rn7Hi5qDMz7Jdbn470dY8XKifG9DP1A=; b=V/6Li+I+jDoJUS6xV1zLb3k6zrU3tsHsZzmfQSkyJ7nS7vH1Sc+LeC//4YXjJFQj1g yxf/lJ5M1S3yNO5IAmKs3YRxLEUVsukhXkERZO4grEDhEX30D7Wrh8i6rOgom1MrbItF SVBvz06XqJkhoNa+LFIuK45K0doFn8ekFbP+uYqnbiKoYMudsKrusonbmhL+4Zt8u/L0 pKLApsauhzmOZrYemEXtLGlgd4Kw0MAdfuqX5CgAgKRJ/0jdy7P+8YSic+YfR7XNoPDs oovjaZR7/3A760Qo55G5FIJYQY50n2hE48bTMi5F//pTYBPh8yZc258/A2j6Td395O66 SJkw== X-Gm-Message-State: APjAAAV2pJPdbXr54b2EhysrhJEF1jyrIKY6L0QX4pQClHa2VzeT6dDk w4ADgAQOkHXdIhaAa2wcH0t0WU+mvhnTMw== X-Google-Smtp-Source: APXvYqyV75LTEDXn7gqyXk9dSeJyCp8eWgdxVbWcJ+F91DcqlgIjgm9yX43AQ+h41N4PF7kkLKLolA== X-Received: by 2002:a25:35d6:: with SMTP id c205mr22697624yba.372.1576534275002; Mon, 16 Dec 2019 14:11:15 -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: <20191216035514.jj7bem3dspnmhdu4@tarpaulin.shahaf.local2> Date: Mon, 16 Dec 2019 16:11:13 -0600 Cc: zsh-workers@zsh.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20191216035514.jj7bem3dspnmhdu4@tarpaulin.shahaf.local2> To: Daniel Shahaf X-Mailer: Apple Mail (2.3445.104.11) On 15 Dec 2019, at 21:55, Daniel Shahaf wrote: > At this point, why don't we change it to X.Y.Z.N-blah I like this idea if you guys do. It's easy to understand and should play = well with just about any version-comparison method. We use a similar scheme = where i work. Pending a decision on that, though... On 15 Dec 2019, at 21:55, Daniel Shahaf wrote: > Suggest: s/appropriate/upcoming/ Done On 15 Dec 2019, at 21:55, Daniel Shahaf wrote: > Please keep whitespace/wrapping changes and substantive changes in = separate > commits. They are otherwise hard to review. Sorry, that was cheeky. I've broken the white-space changes out into a = second patch this time On 15 Dec 2019, at 21:55, Daniel Shahaf wrote: > In principle, it'll be nice to have archived copies of all tarballs I agree, but it doesn't look like we've done that historically, so i = figured i'd just document the process we have now. I think i still don't have = access to zsh.org/pub myself (?), but if i ever get it in the future i can copy = the artefacts over from Sourceforge and update the instructions going = forward dana diff --git a/Etc/creating-a-release.txt b/Etc/creating-a-release.txt index dfde269ae..773a6af8c 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 + upcoming stable version number. + - Commit those changes with an "unposted" ChangeLog entry. =20 git commit -am "Test release: 5.5.1-test-1." && @@ -50,11 +63,11 @@ To create a zsh release: 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,7 +107,7 @@ 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 +- 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@ diff --git a/Etc/creating-a-release.txt b/Etc/creating-a-release.txt index 773a6af8c..417799050 100644 --- a/Etc/creating-a-release.txt +++ b/Etc/creating-a-release.txt @@ -58,7 +58,8 @@ 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 @@ -67,7 +68,10 @@ To create a zsh release: =20 Test releases go to the "zsh-test" directory. Stable releases to zsh/ and zsh-doc/. - 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. + 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 @@ -107,8 +111,8 @@ To create a zsh release: # several minutes to appear afterwards rsync ... =20 -- 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. +- 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