Sorry for not being more explicit. Yes, the milestone gives me a set of PRs whose changes are designated for 1.16
If I were to manually build sources for 1.16 candidate I would 1. create a branch at some SHA in the master, 2. cherry-pick commits from PRs enumerated in milestone/58 not reachable from the chosen SHA. What I am missing is the convention on how to choose the merge-base in step 1. I am interesting in building sources so that I can try to generate patches on top of these sources in advance, and have myself enough time to resolve possible conflicts. Thanks, Sasha From: NumPy-Discussion [mailto:numpy-discussion-bounces+oleksandr.pavlyk=intel....@python.org] On Behalf Of Robert Kern Sent: Thursday, November 29, 2018 1:59 PM To: Discussion of Numerical Python <numpy-discussion@python.org> Subject: Re: [Numpy-discussion] How to get sources of the current state of 1.16? There is a GitHub Milestone for 1.16: https://github.com/numpy/numpy/milestone/58 On Thu, Nov 29, 2018 at 11:54 AM Pavlyk, Oleksandr <oleksandr.pav...@intel.com<mailto:oleksandr.pav...@intel.com>> wrote: Are they the same as the current master, or is there a mechanism to query issue tracker for all PRs designated to make it into 1.16? Even then, what should the base be? Perhaps this is already documented in either an issue or a PR. Thanks for the pointer. Sasha _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org<mailto:NumPy-Discussion@python.org> https://mail.python.org/mailman/listinfo/numpy-discussion -- Robert Kern
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
