On 2013-04-10 15:45:00 -0700, Will Yardley wrote: > On Wed, Apr 10, 2013 at 04:27:29PM +0200, Moritz Barsnick wrote: > > That has been a recurring topic on this list, year over year. :-) > > Sometimes such threads, especially w.r.t. 1.6, initiate(d) a hustle to > > define milestones, clean up some tickets, and increase mailing list > > traffic, but we still haven't reached 1.6, and when was the last 1.5.x > > release? ;-) > > I'm not a developer, but this is along the lines of what I was thinking > would make sense -- why not have a feature freeze for the dev branch, > and not allow any patches with new features until enough bugs are fixed > to release 1.6. If people have to wait for the release for any new > features / patches to be incorporated into dev, maybe it will spark a > little more interest in fixing bugs?
AFAIK, there has been a feature freeze for several years, but nothing happened. IMHO, Mutt 1.6 should be released even though there are remaining bugs; it would still be much better than the latest 1.4.x, which is almost no longer used anyway. First make sure that copyright years are up-to-date, e.g. http://dev.mutt.org/trac/ticket/3476 -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
