zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: Re: Feature freeze for 3.1.6? RE: pws-24
Date: Mon, 28 Jun 1999 15:26:19 +0000	[thread overview]
Message-ID: <990628152619.ZM14150@candle.brasslantern.com> (raw)
In-Reply-To: <9906281002.AA40261@ibmth.df.unipi.it>
In-Reply-To: <001301bec153$2ef4e400$21c9ca95@mow.siemens.ru>

On Jun 28, 12:02pm, Peter Stephenson wrote:
} Subject: Re: Feature freeze for 3.1.6? RE: pws-24
}
} You're right that 3.1.5 and 3.1.6 don't look much alike. [...] How
} about something like 3.1.99? or even 3.99? or something?

On Jun 28,  2:44pm, Andrej Borsenkow wrote:
} Subject: RE: Feature freeze for 3.1.6? RE: pws-24
}
} The vital point is, that 3.1.6 is just a bug fix in this scheme ...
} and more than a year for a bug fix is certainly too much :-)

Personally, I think calling it 3.1.6 will be just fine; there's never
been any statement that the `z' numbers were "bug fixes," only that
the even `y' indicated a stable release and the odd `y' a development
release.

And there was almost a year between 3.1.2 and 3.1.3, with several
zefram-N releases in between, so it's not like we haven't done this
before.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1999-06-28 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-26 14:56 pws-24 Peter Stephenson
1999-06-28 10:05 ` Feature freeze for 3.1.6? pws-24 Andrej Borsenkow
1999-06-28 10:02   ` Peter Stephenson
1999-06-28 10:44     ` Andrej Borsenkow
1999-06-28 15:26       ` Bart Schaefer [this message]
1999-06-28 17:51       ` public CVS archive Peter Stephenson
1999-06-29  9:19         ` Andrej Borsenkow
1999-06-29 12:28           ` Ollivier Robert
1999-06-29 15:53             ` Bart Schaefer

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=990628152619.ZM14150@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --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).