From: Oliver Kiddle <opk@thoth.u-net.com>
To: Peter Stephenson <pws@ibmth.df.unipi.it>, zsh-workers@sunsite.auc.dk
Subject: Re: Change of coordinator
Date: Mon, 07 Jun 1999 14:04:03 +0100 [thread overview]
Message-ID: <375BC343.B637D9BE@thoth.u-net.com> (raw)
In-Reply-To: <9906041243.AA26523@ibmth.df.unipi.it>
Peter Stephenson wrote:
>
> more, so I've been nominated to take over for development of zsh 3.1. This
> should be a fairly seamless transition, since I've been producing
> unofficial intermediate versions for a few months now; these will now
I hope that the frequency of your releases will continue - I've found it
extremely useful to be able to have a very up-to-date version of zsh
without having to constantly apply patches myself. If making an official
release is more time consuming for whatever reason I think continuing to
have unofficial intermediate versions would be a good idea.
> eventually become the official version 3.1.6. I hope this will appear over
Wouldn't it possibly make more sense to call the next official
development release version 3.9.0, working towards a stable version 4.0.
The 20 pws releases are quite a substantial advance from 3.1.5 and it
would make sense for this to be clearer in the version numbering. Also,
I would have thought that the 3.1 advances over 3.0 are approaching
being sufficient for the major version number change?
I wasn't on the mailing lists before version 3 so don't really know how
these things are normally decided or how much of a change to zsh
previously warranted a major version number change so sorry if this is a
stupid suggestion.
Thanks
Oliver Kiddle
next parent reply other threads:[~1999-06-07 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9906041243.AA26523@ibmth.df.unipi.it>
1999-06-07 13:04 ` Oliver Kiddle [this message]
1999-06-08 14:45 ` Peter Stephenson
1999-06-08 19:11 ` Dynamic loading on Solaris 2.7 Danek Duvall
1999-06-09 7:36 ` Peter Stephenson
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=375BC343.B637D9BE@thoth.u-net.com \
--to=opk@thoth.u-net.com \
--cc=pws@ibmth.df.unipi.it \
--cc=zsh-workers@sunsite.auc.dk \
/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).