On 7 March 2018 at 16:28, Sumana Harihareswara <s...@changeset.nyc> wrote:
> On 03/07/2018 11:22 AM, Sumana Harihareswara wrote:
>> I saw today that pip's last release, 9.0.1, was in November 2016.
>> https://pypi.org/project/pip/#history
>>
>> Since that release, 250+ PRs have been merged:
>> https://github.com/pypa/pip/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Amerged+updated%3A%3E%3D2016-11-06
>>
>> I see that a few issues
>> https://github.com/pypa/pip/issues?q=is%3Aopen+is%3Aissue+label%3A%22release+blocker%22
>> are marked as blocking the next release, but are they all blocking *any*
>> next release (such as a 9.0.2 bugfix release), or would it be possible
>> to release soon anyway, while working towards 10.0.0? Or are there
>> backwards-incompatible changes in trunk?
>>
>> -Sumana
>
> Of course, a few minutes after posting this, I see Pradyun's roadmap for
> releasing 10.0 in
> https://github.com/pypa/pip/issues/4981#issuecomment-369495847 .

Yeah, we're pushing for a pip 10 release at the moment. I'm currently
planning on doing that release, but getting the list of blockers
sorted is the current task. I'm hoping to have some time this weekend
to go through the list and see where we're up to and update that
issue.

At the moment,we don't have the infrastructure for doing bugfix
releases - and in this specific situation, pulling out the "ready to
go" parts of master to form an interim release isn't really practical,
given the resources we have. Once pip 10 is out of the door, I'd like
to investigate the possibility of having some sort of "maintenance
branch" setup, but we're so thin on the ground at the moment (with
Donald working on Warehouse and Xavier on leave of absence, it's
basically just Pradyun and I, and I'm not managing to actually work on
code much, just reviews and issue management) so I don't want to
overload what little resource we have with admin.

Paul

Reply via email to