[Pkg-mutt-maintainers] plan for src:mutt bugs now we have src:neomutt

[Antonio Radici]

On Wed, Nov 29, 2017 at 03:22:28PM +0000, Jonathan Dowland wrote:
> Hey,
> 
> Now that we have both src:mutt and src:neomutt in the archive, we need a
> plan for what to do with all the existing bugs filed against src:mutt.
> 
> For example my pet bug #866366 was filed against src:mutt whilst it was
> neomutt and has never applied to mutt upstream (it was broken and then
> fixed in neomutt, and the neomutt package has the fix now)
> 
> So one possibility is all bugs not filed since src:mutt became mutt are
> re-assigned to neomutt. Or we could consider whether really old bugs are
> from before src:mutt was neomutt and not reassign them.
> 
> Or I suppose we could go through every single bug and see whether they
> are reproducible in src:mutt or src:neomutt or both or neither; but
> that's obviously not going to happen!

I have some ideas on which bugs are related to mutt and which are related to
neomutt, I went through all bugs multiple times, and I think that this can be
solved in a couple of hours. In many cases it's clear which bug has the code.

I won't be able to do it this weekend but I can certainly do it next weekend.