zsh-users
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-users@zsh.org
Subject: Re: Test release: 5.6.2-test-3
Date: Sun, 06 Jan 2019 16:35:20 +0000	[thread overview]
Message-ID: <1546792520.3627770.1626942536.5D75D897@webmail.messagingengine.com> (raw)
In-Reply-To: <CAKc7PVDXzSYQ7608HcGhiKu4q3Tyn5Vh77LQPuDGjnq5O+_yfg@mail.gmail.com>

Sebastian Gniazdowski wrote on Sat, 05 Jan 2019 23:31 +0100:
> Shouldn\t the message go to zsh-users instead of zsh-workers? I've
> forwarded it, it's below:

Thanks, and yes, I think the wider audience would be helpful, but at the
same time, we should clarify what guarantees test releases (don't) have.
At Subversion, our release candidate (RC) announcements explicitly (and
somewhat verbosely) say that RC's may have serious bugs and that no
upgrade path is promised:

http://svn.apache.org/repos/asf/subversion/trunk/tools/dist/templates/rc-release-ann.ezt

I would assume zsh pre-releases will have similar (non)-promises.  For
example, don't promise that 5.7 will be backwards compatible with 5.6.2-test-
3; only that it'll be compatible with 5.6.2.

Cheers,

Daniel

> ---------- Forwarded message ---------
> From: dana <dana@dana.is>
> Date: Sat, 5 Jan 2019 at 08:06
> Subject: Test release: 5.6.2-test-3
> To: Zsh workers <zsh-workers@zsh.org>
> 
> 
> I've tagged 5.6.2-test-3 and uploaded the artefacts to:
> 
> https://sourceforge.net/projects/zsh/files/zsh-test/5.6.2-test-3
> 
> Hope i did this right. If someone could please glance at it to make sure that
> would be nice. Thanks Daniel and Peter for helping me.
> 
> PS: Building the docs on macOS is an insane ordeal. After messing with it for
> almost an hour i finally got to the point where i had to install X11 to
> generate the PDF and decided it just wasn't worth it. I ended up building on
> an old Linux lap-top. If anyone's done this on macOS before and knows a trick
> to it that doesn't require a million weird dependencies, please let me know
> 
> PPS: Notes/docs on zsh.org were never updated for 5.6.x. I haven't done that
> now, but i'll look into it later
> 
> dana

      reply	other threads:[~2019-01-06 16:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <C0CF1A8E-FD75-4024-BA4B-0C4D8880FB8D@dana.is>
2019-01-05 22:31 ` Sebastian Gniazdowski
2019-01-06 16:35   ` Daniel Shahaf [this message]

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=1546792520.3627770.1626942536.5D75D897@webmail.messagingengine.com \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).