From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13789 invoked from network); 11 Jun 2007 22:12:42 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=no version=3.2.0 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by ns1.primenet.com.au with SMTP; 11 Jun 2007 22:12:42 -0000 Received-SPF: none (ns1.primenet.com.au: domain at sunsite.dk does not designate permitted sender hosts) Received: (qmail 48666 invoked from network); 11 Jun 2007 22:12:36 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 11 Jun 2007 22:12:36 -0000 Received: (qmail 12689 invoked by alias); 11 Jun 2007 22:12:33 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 23550 Received: (qmail 12679 invoked from network); 11 Jun 2007 22:12:32 -0000 Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88) by sunsite.dk with SMTP; 11 Jun 2007 22:12:32 -0000 Received: (qmail 48400 invoked from network); 11 Jun 2007 22:12:32 -0000 Received: from mtaout01-winn.ispmail.ntl.com (81.103.221.47) by a.mx.sunsite.dk with SMTP; 11 Jun 2007 22:12:28 -0000 Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout01-winn.ispmail.ntl.com with ESMTP id <20070611221227.ECOW12936.mtaout01-winn.ispmail.ntl.com@aamtaout01-winn.ispmail.ntl.com> for ; Mon, 11 Jun 2007 23:12:27 +0100 Received: from pwslaptop.csr.com ([81.107.45.67]) by aamtaout01-winn.ispmail.ntl.com with ESMTP id <20070611221227.GUQR219.aamtaout01-winn.ispmail.ntl.com@pwslaptop.csr.com> for ; Mon, 11 Jun 2007 23:12:27 +0100 Received: from pwslaptop.csr.com (pwslaptop.csr.com [127.0.0.1]) by pwslaptop.csr.com (8.13.8/8.13.7) with ESMTP id l5BMAH2T003653 for ; Mon, 11 Jun 2007 23:10:18 +0100 Message-Id: <200706112210.l5BMAH2T003653@pwslaptop.csr.com> From: Peter Stephenson To: zsh-workers@sunsite.dk Subject: Re: zsh stable release, or is 4.3.4 stable enough for Fedora? In-Reply-To: Message from "Caio Marcelo" of "Mon, 11 Jun 2007 14:03:44 -0300." Date: Mon, 11 Jun 2007 23:10:17 +0100 "Caio Marcelo" wrote: > Hello, > > Is there any plan of releasing a new "stable" release of zsh in the > near future? Or the stable/unstable convention isn't being used > anymore? 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. What I'm looking for before producing a new stable release (which will probably be version 5) are signs that the multibyte support in 4.3 is complete enough that most users aren't going to find significant gaps. It doesn't have to be flawless. At some point we need to decide that things are working well enough. With Linux, I think that's already the case, but I'm less clear about the state of other systems I don't see. (I've also been worrying about completion inside nested quotes---it's a fairly minor feature but it's also fairly badly messed up and fixing it is likely to be a struggle. I also need to complete the module feature support; that's not so difficult but will needs some time.) This doesn't answer the question about when it's going to appear because I don't yet know. > I'm asking this because Fedora is holding to update zsh package (today > it's 4.2.6, from 2005-12-05) because 4.3.x versions are considered > unstable. On the other hand updating would be very useful because of > Unicode stuff in newer zsh. Maybe it would be fine to Fedora update to > 4.3.4? Ubuntu have been using 4.3.x sincfe last year. 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. This isn't going to get much longer before version 5; the biggest likely one is an option to fix the kludges described in the recent threads about (R) subscripting (see for example the "Change in FIGNORE behaviour" thread). -- Peter Stephenson Web page now at http://homepage.ntlworld.com/p.w.stephenson/