zsh-workers
 help / color / mirror / code / Atom feed
From: "Caio Marcelo" <cmarcelo@gmail.com>
To: "Peter Stephenson" <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: zsh stable release, or is 4.3.4 stable enough for Fedora?
Date: Mon, 11 Jun 2007 20:21:17 -0300	[thread overview]
Message-ID: <d280d7f10706111621t25dd31bfs82f7c30a6ce1be8c@mail.gmail.com> (raw)
In-Reply-To: <200706112210.l5BMAH2T003653@pwslaptop.csr.com>

Hello,

On 6/11/07, Peter Stephenson <p.w.stephenson@ntlworld.com> wrote:
> Strictly speaking, 4.3.4 isn't stable in quite the same way 4.2 is.
> How ever, that's less because it's broken than because it's a moving
> target; "unstable" means "it keeps changing" rather than "it doesn't
> work".  I don't think there are big problems with broken code.

> (...)

> This doesn't answer the question about when it's going to appear because
> I don't yet know.

Thanks for the detailed update on the project status.


> On balance, I think most users would probably benefit from upgrading.
> The thing to worry about is less stability in terms of bugs, since I
> don't see much evidence that's a problem, and more stability in terms of
> features; see for example the list of incompatibilities in the README
> file.

>From my (little) experience, what you said and the fact that both
Ubuntu and Gentoo (other well-known distros) are already using 4.3.x
somehow, I think it's time to Fedora go this way too. Anyway, I'll
report your answer in Fedora bugzilla and see what the package
maintainers think about.


Cheers,
  Caio Marcelo


      reply	other threads:[~2007-06-11 23:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cmarcelo@gmail.com>
2007-06-11 17:03 ` Caio Marcelo
2007-06-11 22:10   ` Peter Stephenson
2007-06-11 23:21     ` Caio Marcelo [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=d280d7f10706111621t25dd31bfs82f7c30a6ce1be8c@mail.gmail.com \
    --to=cmarcelo@gmail.com \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@sunsite.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).