From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4806 invoked by alias); 19 Jan 2014 12:01:46 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32287 Received: (qmail 2518 invoked from network); 19 Jan 2014 12:01:41 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.2 Date: Sun, 19 Jan 2014 13:01:38 +0100 From: Axel Beckert To: zsh-workers@zsh.org Subject: Bug reports after releases (was: Re: Bug with long multiline strings?) Message-ID: <20140119120137.GI27889@sym.noone.org> Mail-Followup-To: zsh-workers@zsh.org References: <87vcdzq4ke.fsf@ft.bewatermyfriend.org> <20121024171023.313995d7@pwslap01u.europe.root.pri> <20121025095936.621c7717@pws-pc.ntlworld.com> <87bofqq54z.fsf@ft.bewatermyfriend.org> <87sism8ie6.fsf@ft.bewatermyfriend.org> <140118133407.ZM10286@torch.brasslantern.com> <140118205928.ZM11152@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <140118205928.ZM11152@torch.brasslantern.com> X-Operating-System: Linux 2.6.32-5-xen-amd64 X-Machine: sym2 x86_64 X-Editor: GNU Emacs 23.2.1 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAAAAAC3mUtaAAAABGdBTUEAALGPC/xhBQAAADh0RVh0U29mdHdhcmUAWFYgVmVyc2lvbiAzLjEwYSAgUmV2OiAxMi8yOS85NCAoUE5HIHBhdGNoIDEuMindFS5JAAACGElEQVQ4jXXQMU8UYRDG8f8shNjdDH4AbpfGDjAWlKiJiZ0ajL1aGCvsNCbGaCGG1koLaztaTYz6ATy+gOyehYmF3MxVxgg3FnDsHcTpJr/M+8w7Rf6nCsaVTTDqxbg9hoOXmw83H71+Eyfg4E1d7/Z2fG9rGkZbTQiu+K+3U/C+76lmkvAhJuDndnoAiftou4V84okAGclop4U/jYACZDTxrYWP0gkxVfAm/W//GLZpxIzwIN0Hn8dw0B+IWkZmQmRsj2HfhwokEklHfNCCiQCRgAR7YyhQVRVTCKCzP4Y5zBBE0t0zY3Q8oQaBqqAMlVEcgVQd9706zGirAFium8HXumlMIeMwqQCInju+2+uB6MRENupdpMt8pRlHZyuAW0F+Mb6XSIVqtxjD+iVmVqqystLEzFTGT92YqRaXpNT5eTVjeJhbALPnrTxLUZUKZsgxcNm64hAOYisT/xhF+oKTGU5RegtC3Rt6eEDi/QnIevdTx9Md2EMmYBRmCQR1026FCGQQJJExsRUqgkMGaWSbwYLnoO4T6VgpbQbdELPMBAHWWrhYrcxXnYgAsatPWygkFCBD4K62MAsOTqA6szYRPpsu6e6Y8mPiVrBMNuGIMrgwBUu4p2DgG1Ownu6hpuTv7hScefHAzAC/yRRw5U5pALMbJ4AUALvHSZhxgHPXTsHcdWD1GadAHr9avP+c0wCr7263Df8ASLwXWHWs+KIAAAAHdElNRQfYBQEBODPr Organization: DeuxChevaux.org -- The =?iso-8859-1?Q?Citr?= =?iso-8859-1?B?b+tu?= 2CV Database User-Agent: Mutt/1.5.20 (2009-06-14) Hi, On Sat, Jan 18, 2014 at 08:59:28PM -0800, Bart Schaefer wrote: > I imagine Peter is getting rather tired of crash bugs getting found and > fixed only days after he does a release. Well, trigger was likely the fact that this bug had some activity on Ubuntu's Launchpad after someone was able to reproduce it with 5.0.5 in Debian. Since that bug had multiple reports which weren't merged, I started to review _all_ segfault causing bugs reported in Debian and Ubuntu for duplicates, and secondarily also for not being forwarded to zsh-workers, but reproducible. Hence that bunch of forwarded bugs this weekend. We recently had that topic of bugs being found _after_ releases (or in case of distributions after uploads of binary packages) also on #pkg-zsh (Freenode IRC network, home of Debian's zsh packages) and we came to the conclusion that it's quite common: Once a release is done, it triggers a bunch of activity which again triggers a bunch of bug-reports. This can be nicely seen in the zsh 5.0.x releases: 5.0.0 lasted long, 5.0.1 didn't. 5.0.2 lasted long, 5.0.3 and 5.0.4 didn't. "-test" releases help, but only reach a small (but active) group. Uploading just to http://www.zsh.org/pub/ but not SourceForge and sending the announcement only to zsh-workers/-users and not zsh-announce clearly helps further as seen with 5.0.3 and 5.0.4. But some corner-case issues are only found after a release is out or even only after it propagated into the stable releases of some popular Linux or BSD distributions... (Yeah, somehow this feels like boiling down to "release early, release often". :-) But back to the current situation: All those recently fixed bug reports about crashes (at least those reports where I was involved) are bugs which exist for quite a long time (over 1 year at least), so I don't think there's any kind of urgency to make a new release just because of them. (Of course I wouldn't mind if they would trigger a release. :-) Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | abe@deuxchevaux.org (Mail) X See http://www.nonhtmlmail.org/campaign.html | abe@noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)