help / color / mirror / code / Atom feed
From: Axel Beckert <abe@deuxchevaux.org>
To: zsh-workers@zsh.org
Subject: Re: Posted zsh 5.9
Date: Sun, 15 May 2022 01:35:41 +0200	[thread overview]
Message-ID: <20220514233540.pf22yphhsjm4tblf@sym.noone.org> (raw)
In-Reply-To: <20220514232126.GA13240@tarpaulin.shahaf.local2>

Hi Daniel,

On Sat, May 14, 2022 at 11:21:26PM +0000, Daniel Shahaf wrote:
> Axel Beckert wrote on Sun, May 15, 2022 at 00:11:31 +0200:
> > Hi,
> > 
> > On Sat, May 14, 2022 at 03:59:35PM -0500, dana wrote:
> > > I've just finished posting zsh 5.9. It should be available in the usual
> > > places:
> > […]
> > > creating-a-release instructs us to wait a day before posting to -announce,
> > > which has always been followed a little loosely i think, at least by me...
> > > but i'll do that this time, unless someone wants me to go ahead now.
> > 
> > I'll upload it to Debian unstable anyway, I as I assume there won't be
> > any changes anymore until tomorrow. :-)
> I'd rather you didn't.  Backwards compatibility promises don't kick in
> until a release is announced, even if it has been tagged.

IMHO having been uploaded is a bit more than just tagged.

> If we pull the tarball for any reason, your users will get to keep
> both pieces.

If that happens, I'd expect that a 5.9.1 or 5.9a or something is
released and 5.9 is never annouced. Like e.g. the ASF does with HTTPD
releases. Not every 2.4.xy or 2.6.xy has been released (or at least
not announced).

The tar ball is btw. already imported and pushed to Debian's packaging
git repo. I haven't uploaded though, so I'll postpone that until
tomorrow (or rather later today depending on the timezone :-).

> Cf. https://dist.apache.org/repos/dist/dev/subversion/README.html.

That talks about release candidates, not about already publicly
downloadable tar balls with the correct version. Our -test releases
are the release candidates from my point of view. And yes, of course I
fully agree with that. That's why I uploaded all packages of release
candidates to Debian Experimental, not to Unstable.

According to discusion in here, the reasons for the delay are also
others. (I also remember from earlier discussions about the release
process that SF's upload thingy is a bit fiddly and sometimes needs a
few attempts to get their "newest upload" pointer right.)

		Kind regards, Axel
PGP: 2FF9CD59612616B5      /~\  Plain Text Ribbon Campaign, http://arc.pasp.de/
Mail: abe@deuxchevaux.org  \ /  Say No to HTML in E-Mail and Usenet
Mail+Jabber: abe@noone.org  X
https://axel.beckert.ch/   / \  I love long mails: https://email.is-not-s.ms/

  reply	other threads:[~2022-05-14 23:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 20:59 dana
2022-05-14 21:50 ` Daniel Shahaf
2022-05-14 21:58   ` Daniel Shahaf
2022-05-14 22:27   ` dana
2022-05-14 23:26     ` Daniel Shahaf
2022-05-14 23:28     ` Daniel Shahaf
2022-05-14 23:50       ` dana
2022-05-15 10:36         ` Daniel Shahaf
2022-05-15 21:43           ` dana
2022-05-16 23:57   ` Phil Pennock
2022-05-21  1:31     ` Daniel Shahaf
2022-05-14 22:11 ` Axel Beckert
2022-05-14 22:31   ` dana
2022-05-15  4:33     ` Bart Schaefer
2022-05-15  6:00       ` dana
2022-05-14 23:21   ` Daniel Shahaf
2022-05-14 23:35     ` Axel Beckert [this message]
2022-05-14 23:49       ` Daniel Shahaf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220514233540.pf22yphhsjm4tblf@sym.noone.org \
    --to=abe@deuxchevaux.org \
    --cc=zsh-workers@zsh.org \
    --subject='Re: Posted zsh 5.9' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).