[moving this to its own thread]

On Sun, Nov 22, 2015 at 03:09:39PM -0600, David Champion wrote:
> * On 22 Nov 2015, Kevin J. McCarthy wrote: 
> > Personally, and I haven't discussed this with the other committers yet,
> > I would like to release a 1.5.25 around February and try for a 1.6.0
> > August of next year.
> 
> My feeling has long been that because 1.5 has become considerably more
> complete than 1.4, and because it's been in common non-development use
> for so long, it has already become the de facto "production" release.
> I think we could relegate the even/odd versioning to history, apply a
> 1.6 tag as soon as we clear all in-flight bugfix patches, and continue
> with only one tagged series from there.  (Development would simply be
> untagged.)

I believe we're on the same page here.  I was originally thinking about
one more 1.5.x release just to give more time, but I'm definitely open
to just pushing straight for a 1.6.0 as the next release.  Recently,
I've mostly been focusing on bug fixes; I have the SMTPUTF8 series I'd
like to commit, but otherwise think a good next step would be working on
any major bugs and reviewing external patches.

I'm also open to moving away from an odd/even scheme, and just having
releases.  Our current stable/default branches do work well though, so
I'd like to keep using those as we are today, to be able to quickly
release security fixes if needed.

> > During that time, I would like to take a look at a few of the external
> > patches.  Someone requested the trash patch, for one.
> 
> I agree this would be a good step.  We started that review with Debian
> patches a while back but I don't think we finished.
> 
> Mutt is a pretty aged project, with a lot of third-party patches.  A
> major consideration with patch merges at this stage of a project's
> lifespan is maintenance responsibility - committer time is in short
> supply, so we must be cautious what committers take full responsibility
> for.

That makes sense to me.  It would be good to take a look at Debian and
Gentoo's patches (any others?), but with an eye towards not taking on
anything too crazy before 1.6.0.

I know you have an extensive list of patches you maintain.  Are
there any you'd like to get committed before 1.6.0?  What about the
command-on-new-mail series?  (No pressure, just asking...)

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA
http://www.8t8.us/configs/gpg-key-transition-statement.txt

Attachment: signature.asc
Description: PGP signature

Reply via email to