>> And all of this work would be saved if mutt upstream released new >> versions more frequently. > > 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 agree. Long times between releases are people/devs trying to build personal perfection and of unending innumerous features and only hold projects back. A release should happen when you've got somethng that builds and 'hey, this has been in for a while lets roll with it'. (Backed up with commitment to fixing any bugs in that.) Especially concerning releases of any fix branches as opposed to feature branches. In the open source world, when you go for 6 months or more, you look dead and suspect as a vibrant open source project. And rightly so. That's sad... upon a project, not necessarily the open source model. After all, surely there was some subset of pure bugs that could have been rolled.
