How about tagging a new release

[GuillaumeSeren]

Hey,
it's been a while since the last release (~2 years since the 3.0.1),
I would like to suggest a new release we had quite some work done,
and the python target used back then have to upgraded to something up-to-date.

What do you think ?

[hendursaga]

Who's in charge of this?

[GuillaumeSeren]

@flokli what do you think ?

[flokli]

Sorry, only saw this now.

I did #333 recently, because I was getting readthedocs emails, and added a 3.1.0 section in NEWS.md.

I guess what's needed for this is going through the git commits since 3.0.0 and 3.1.0 to see what else has happened since then, and update the document.

[flokli]

Things I see so far:

• Handle DMARC report with empty spf or dkim XML nodes #305
• DMARC Filter: allow to define subject regexp #332
• Upgrade python support #329 (maybe already covered)
• Get notmuch database path using Database wrapper #321
• fix typo in DKIM filter docs #318 (minor)
• HeaderMatchingFilter: do not convert user supplied tags #315

@GuillaumeSeren considering you were involved in most of these PRs, can you take a look and send a PR adding some summaries to NEWS.md?

[GuillaumeSeren]

Hey,
good to see you !

Yes I will prepare a PR with the needed changes in the NEWS.md 📝

[GuillaumeSeren]

Maybe we could get #307 as well ?

[flokli]

With #334 in, I'd say let's cut a release now, and not delay it much further.

[flokli]

We can still do another release afterwards.

[GuillaumeSeren]

Sure let's check others patches later and finish this release as it is.