> On Oct 26, 2015, at 11:57 AM, Jonathan Vanasco
> wrote:
>
> From a "non-core user" of twisted point of view, and someone likely to run
> into issues from this change... things that I have liked from other projects
> are:
Thanks very much (and thanks to everyone else as well) for sharing y
On Oct 25, 2015, at 11:34 PM, Glyph Lefkowitz wrote:
> For another, we have no way to hide deprecated APIs in the API documentation.
> If a new user is trying to figure out how to do something, if they're doing
> it during the deprecation period, they should not start out by using a
> depreca
> On Oct 25, 2015, at 5:48 PM, Amber Hawkie Brown
> wrote:
>
> Hi everyone,
>
> As many know, one of the things that makes the Twisted project so unique is
> our conformance to our Compatibility Policy. This policy means that users of
> Twisted can freely upgrade between versions with all in
This is a reasonable change.
I say that as someone who rarely tracks individual Twisted releases. We
typically upgrade client-deployed applications every three to five years
(at the moment, I’m working on upgrading several projects from 12.1 to
15.4).
For us, being able to easily track back throu
