Re: [Mailman-Developers] Next Postorius release

2017-06-30 Thread Barry Warsaw
On Jun 30, 2017, at 07:24 PM, Abhilash Raj wrote: >Have you looked at Mariatta's new cherry-picker tool for CPython >workflow? It seems to make the cherry-picking and backporting a bit easier. > >[1]: https://github.com/python/core-workflow/tree/master/cherry_picker I haven't yet used it for CPyt

Re: [Mailman-Developers] Next Postorius release

2017-06-30 Thread Abhilash Raj
Excerpts from Barry Warsaw's message of June 30, 2017 1:15 pm: On Jun 30, 2017, at 07:24 PM, Abhilash Raj wrote: Have you looked at Mariatta's new cherry-picker tool for CPython workflow? It seems to make the cherry-picking and backporting a bit easier. [1]: https://github.com/python/core-work

Re: [Mailman-Developers] Next Postorius release

2017-06-30 Thread Abhilash Raj
Excerpts from Barry Warsaw's message of June 30, 2017 7:33 am: It still of course means we have to find the resources to do the cherry picks and releases. :( Have you looked at Mariatta's new cherry-picker tool for CPython workflow? It seems to make the cherry-picking and backporting a bit eas

Re: [Mailman-Developers] Next Postorius release

2017-06-30 Thread Barry Warsaw
On Jun 30, 2017, at 02:21 PM, Simon Hanna wrote: >I know it might be a little early, but I'd like to talk about the plan >for Postorius (Mailman in general) releases moving forward. > >Should there be more point releases? 3.1.X? Or just 3.X? Are releases >bound to Core releases (following core's r