Release 19.0 -- New year, New release

[pradyunsg]

Yet another issue for discussing yet another release. :)

[pradyunsg]

This one is a release with some heavy weight issues given that PEP 517 and manylinux2010 support are a part of it. There's also a bunch of "nicer error message" and VCS improvements here.

There's enough to justify a release here, clearly. I'm willing to be the RM for this release.

A quick question to @pfmoore, do you reckon PEP 517 should spend some time in a "beta" phase before being released?

[pfmoore]

If you mean do we need a prerelease, I don't think so. It's not something we've done that often in the past, and the PEP 517 changes should default back to legacy processing, so I'd be OK just going for a normal release. In my experience, very few people actually test the betas anyway.

I'm not against a beta (I think it would be better if we did have a standard process of doing prereleases) but I don't think the PEP 517 changes warrant one on their own.

[pradyunsg]

That's what I meant.

We do have a standard process in terms of pre-releases in release cycles - if there's a pre-release, the main release is pushed ahead a month. It's documented in our release cadence docs.

[pfmoore]

We do have a standard process in terms of pre-releases in release cycles

What I meant was that I think we should routinely do prereleases, but thinking more about it, with releases every 3 months, prereleases are too much additional burden (and it's not like we'd get that much additional testing if we did do prereleases...) So just ignore that aside of mine.

[xavfernandez]

While I think about it, it would be nice if a new packaging version could be released and vendored with pypa/packaging@eb02438

[pradyunsg]

I can do a release of packaging - assuming @dstufft doesn't mind that, and merging a PR or giving me push access. :)

[xavfernandez]

And we might want to add a deprecation warning for Python 3.4 support ?
19.0 might be the last version supporting 3.4 ?

[pradyunsg]

I don't think we need a deprecation warning for that. We usually drop versions when the usage is low on PyPI.

I haven't run the bigquery SQL query to check what the numbers are, to facilitate us deciding that.

[xavfernandez]

According to PyPI Stats, Python 3.4 represents ~3% of downloads.

If we plan to drop support for 3.4 in 19.1, we'll want a deprecation warning in 19.0 (à la 90b3db4#diff-84e592bd8e56a3c31ef7f6908753e4feL201).

[pfmoore]

+1 for dropping 3.4 in 19.1 and warning now.

[pradyunsg]

Cool; let's do that.