zsh-workers
 help / color / mirror / code / Atom feed
From: Wayne Davison <wayne@clari.net>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu
Subject: Preparing to release 3.0
Date: Mon, 29 Jul 1996 11:14:18 -0700	[thread overview]
Message-ID: <199607291814.LAA03614@bebop.clari.net> (raw)
In-Reply-To: hzoli's message of Mon, 29 Jul 1996 12:16:02 +0200. <199607291016.MAA00990@bolyai.cs.elte.hu>

I said:
> > Is 3.0 supposed to be a really stable release?  Or is 3.0 supposed to be
> > a work-the-kinks-out-for-3.1 release?

Zoltan Hidvegi writes:
> I think that 3.0-pre4 is already quite stable. [...] There may be some
> coding bugs of course but these are usually trivially fixed by a one-line
> patch.

My question of stability was more about code-base stability and the
trivial bugs, not crashing.  A flurry of one-line patches to fix trivial
bugs in 3.0 is what we want to avoid as much as possible.  We need to
ensure that the recent trap changes are free of trivial problems (like
the BUG bug), and that the recent brace changes are as well, etc.

Why don't we declare the upcoming zsh pre5 "frozen" (basically pre4 with
the latest patches)?  It will remain unchanged except for bug fixes
deemed necessary for release.  Then we can pound on it for a while and
after a couple weeks of code-base stability, decide if we believe 3.0 is
ready for release.

..wayne..


  parent reply	other threads:[~1996-07-29 20:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-28 21:03 Patches missing from pre4? 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       ` Wayne Davison [this message]
1996-07-29 14:04   ` Carlos Carvalho
1996-07-29 12:57     ` Zoltan Hidvegi
1996-07-29 15:43       ` Carlos Carvalho
1996-07-29 14:24         ` Vinnie Shelton

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=199607291814.LAA03614@bebop.clari.net \
    --to=wayne@clari.net \
    --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).