zsh-workers
 help / color / mirror / code / Atom feed
From: Jos Backus <Jos.Backus@nl.origin-it.com>
To: Greg Badros <gjb@cs.washington.edu>
Cc: Peter Stephenson <pws@ibmth.df.unipi.it>, zsh-workers@sunsite.auc.dk
Subject: Re: 3.0.6?
Date: Thu, 25 Feb 1999 12:42:34 +0100	[thread overview]
Message-ID: <19990225124234.B492@hal.mpn.cp.philips.com> (raw)
In-Reply-To: <qrrpv6z2ytk.fsf@elwha.cs.washington.edu>; from Greg Badros on Wed, Feb 24, 1999 at 02:59:03PM -0800

On Wed, Feb 24, 1999 at 02:59:03PM -0800, Greg Badros wrote:
> Can I propose that someone volunteer to put together a 3.0.6 release,

I wonder how much work this would be. It would definitely help with keeping
zsh on the radar screen.

Maybe a very short final testing period would be a good idea after rolling a
candidate release, too.

> and someone (perhaps else) step forward to be the 3.1.x maintainer?

/me ducks :-)

Seriously, I consider myself to be rather underqualified for this task, sorry.

Cheers,
-- 
Jos Backus                          _/  _/_/_/    "Reliability means never
                                   _/  _/   _/     having to say you're sorry."
                                  _/  _/_/_/               -- D. J. Bernstein
                             _/  _/  _/    _/
Jos.Backus@nl.origin-it.com  _/_/   _/_/_/        use Std::Disclaimer;


  reply	other threads:[~1999-02-25 12:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-24  9:43 completion test suggestion Sven Wischnowsky
1999-02-24 12:05 ` 3.0.6? Jos Backus
1999-02-24 13:04   ` 3.0.6? Peter Stephenson
1999-02-24 15:17     ` 3.0.6? Jos Backus
1999-02-24 22:59     ` 3.0.6? Greg Badros
1999-02-25 11:42       ` Jos Backus [this message]
1999-02-25 22:04         ` 3.0.6? Geoff Wing
1999-02-25 22:26           ` 3.0.6? Bart Schaefer
1999-03-08 23:34           ` 3.0.6? Phil Pennock
1999-03-08 23:42             ` 3.0.6? Phil Pennock

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=19990225124234.B492@hal.mpn.cp.philips.com \
    --to=jos.backus@nl.origin-it.com \
    --cc=gjb@cs.washington.edu \
    --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).