This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.moore
Recipients Marcus.Smith, dstufft, ncoghlan, ned.deily, paul.moore, serhiy.storchaka
Date 2018-04-15.10:33:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1523788418.23.0.682650639539.issue33131@psf.upfronthosting.co.za>
In-reply-to
Content
Pip 10 has now been released. I'll be getting a PR to put it into 3.7 in the next few days. One question on workflow - is the right approach to create a PR for master and request a backport to the 3.7 branch? Or is there something else I should do?

Also, can I just check the timing implications should we need to do a 10.0.1 followup release? Would we need to have that released in time for b4, or would it be acceptable to update to 10.0.1 between b4 and rc1? (I'm not trying to push for any particular decision here - we may not even need a 10.0.1 - just want to be sure of the rules).
History
Date User Action Args
2018-04-15 10:33:38paul.mooresetrecipients: + paul.moore, ncoghlan, ned.deily, serhiy.storchaka, dstufft, Marcus.Smith
2018-04-15 10:33:38paul.mooresetmessageid: <1523788418.23.0.682650639539.issue33131@psf.upfronthosting.co.za>
2018-04-15 10:33:38paul.moorelinkissue33131 messages
2018-04-15 10:33:37paul.moorecreate