[Pkg-mutt-maintainers] mutt-1.6.2, or neomutt?

[Faidon Liambotis]

Hi Kevin,

On Mon, Aug 08, 2016 at 02:24:46PM -0700, Kevin J. McCarthy wrote:
> I don't think there is necessarily a need to block or roll-back the
> current unstable 1.6.2-1.  It would be nice if the three commits I
> mentioned before could be added to a 1.6.2-2 release, if that's not a
> lot of work (not sure if they apply cleanly).  Alternatively, I will be
> releasing 1.7.0 in about 2-3 weeks.

I just uploaded a 1.6.2-2 that contains these three commits. I also
briefly touched base with Richard and he said he has imported this into
the neomutt git, so they'll make it on the next neomutt release as well.

I am definitely looking forward to 1.7.0 too :)

> This is definitely in your purview, but I personally would feel better
> to see the patches separated.  At the least, it gives me something to
> look at and evaluate applying individually.

My understanding is that Richard is going through a lot of extra hoops
to provide all the neomutt patches into separate git branches and
separate broken-out unified diffs, precisely so that they can be
upstream material. Is that not an accurate understanding?

> A concern I have is that it feels like NeoMutt has taken about _every_
> patch out there and merged it.  Perhaps some of them should have been
> merged a long time ago, but I'm concerned others shouldn't have been
> (and should not be).  I'm also concerned that once exposed to Debian
> users, some may turn into another "nntp patch" that can never be taken
> away.  So this is yet another reason I'd feel better if you had them
> broken down and knew exactly what features you were adding.

That is definitely a legitimate concern. Do you know already of any
specific patches that you have doubts over?
 
> I agree.  In fact, one thing I could really use help with is
> prioritizing patches and forwarded tickets.
> 
> The compressed folders patch is high on my list, but I'd really like to
> hear from you what priority you consider other patches to be.
> 
> The same with tickets.  I've tried to go through them, but with 570 open
> tickets it's really hard to know where to start sometimes.  If there are
> pain points you know about, pinging a ticket would help put it on my
> radar.

Ack. That's a valid criticism. I'll personally try to be a better
upstream citizen and participate in your bug tracker.

> Okay, I can understand that.  I'd very much like to hear from any of you
> in mutt-dev, the ticket system, or directly.  Please be assured that I'm
> listening and your input will be taken seriously.

Thank you for this, Kevin. Very much appreciated.

Best,
Faidon