On Dec 24, 2016, at 6:01 AM, ex vito <ex.vitorino@gmail.com> wrote:

On 2016-12-23, at 21:22, Glyph Lefkowitz <glyph@twistedmatrix.com> wrote:

On Dec 23, 2016, at 12:31 PM, Glyph Lefkowitz <glyph@twistedmatrix.com> wrote:

On Dec 23, 2016, at 3:49 AM, ex vito <ex.vitorino@gmail.com> wrote:

On 2016-12-23, at 4:33, Amber Hawkie Brown <hawkowl@atleastfornow.net> wrote:

[...]

You can get the tarball and the NEWS file at https://twistedmatrix.com/Releases/rc/16.7.0rc1/ , or you can try it out from PyPI:

    python -m pip install Twisted==16.7.0rc1

Please test it, and let me know how your applications fare, good or bad! If nothing comes up, 16.7 looks like it'll land just before the new year.


Amber,

As far as I can tell, it's been reviewed and approved for merging. If not, please point out what should be improved.

Amber is the release manager and therefore has final say, but, generally, we try not to roll more things into releases.  Instead, we try to roll releases more frequently (which has been a resounding success during 2016, and hopefully we can keep that momentum during 2017).

However, I have to say I'm very sorry this did not get merged in a timely way!  It seems I didn't get the github notification when you @mentioned me; I have no idea why that would be.

I'll get test results on trunk and get it merged, and it should be in the next 17.x release.

Glyph,

The next 17.x release sounds good. I'm in no hurries and that keeps an open time window to address the very tightly related https://twistedmatrix.com/trac/ticket/8912 which I recently noted was created by Tom Prince.

Great.  Basically, try not to worry about releases too much - just do the work as quick as you can, do reviews to speed along the queue in general, and the ever-faster release cadence that Amber has put in place will catch your changes soon enough.


On a related note - this still linked the '#' syntax back to the ticket number in Trac.

Perhaps related - tomprince fixed the bugs that were preventing us from upgrading us to 1.2, and upgraded us to 1.2.  So perhaps this has introduced a problem :).

Thanks for the quick feedback and heads up on the '#' link.

This was a heads-up for Jean-Paul, who has been trying to change this behavior (to make '#' on new commits refer to Github issues / PRs, and 'ticket:' refer to Trac tickets, so we don't get spurious email notifications about old Trac tickets).  You can pretty much ignore it :).

-glyph