zsh-workers
 help / color / mirror / code / Atom feed
From: Vinnie Shelton  <shelton@icd.teradyne.com>
To: Carlos Carvalho <carlos@riglos.fisica.ufpr.br>
Cc: Zoltan Hidvegi <hzoli@cs.elte.hu>, zsh-workers@math.gatech.edu
Subject: Re: Patches missing from pre4?
Date: Mon, 29 Jul 1996 10:24:13 -0400	[thread overview]
Message-ID: <199607291424.KAA13618@spacely.icd.teradyne.com> (raw)
In-Reply-To: carlos's message of Mon, 29 Jul 1996 10:43:00 -0500. <m0uksbM-00002uC@riglos.fisica.ufpr.br>


carlos@riglos.fisica.ufpr.br said:
>  What I mean is that there have been significant changes at each new 
> pre- release, so I think we should wait somewhat longer before making 
> the official release. On the other hand, since you're leaving for 
> hollidays, it'd be nice to have another pre with all the latest 
> fixes, so that the list can pound on it. Another advantage is that we 
> don't have to apply the patches by hand :-)

> Anyway, it's a bad idea to make an official release just before an 
> absence period of the maintainer.

This is absolutely correct on both counts as far as I'm concerned.  Zoltan, 
I'd like to see a pre-5 release just before you go away on vacation, and if no 
bugs are found in that version, to release that as 3.0 upon your return.

My $.02.

--vin


      reply	other threads:[~1996-07-29 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-28 21:03 Bart Schaefer
1996-07-28 22:00 ` Zoltan Hidvegi
1996-07-29  3:14   ` Wayne Davison
1996-07-29 10:16     ` Zoltan Hidvegi
1996-07-29 13:56       ` Carlos Carvalho
1996-07-29 18:14       ` Preparing to release 3.0 Wayne Davison
1996-07-29 14:04   ` Patches missing from pre4? Carlos Carvalho
1996-07-29 12:57     ` Zoltan Hidvegi
1996-07-29 15:43       ` Carlos Carvalho
1996-07-29 14:24         ` Vinnie Shelton [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=199607291424.KAA13618@spacely.icd.teradyne.com \
    --to=shelton@icd.teradyne.com \
    --cc=acs@world.std.com \
    --cc=carlos@riglos.fisica.ufpr.br \
    --cc=hzoli@cs.elte.hu \
    --cc=zsh-workers@math.gatech.edu \
    /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).