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
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> 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 i
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
n
On Thu, Nov 29, 2018 at 2:38 PM Pavlyk, Oleksandr <
oleksandr.pav...@intel.com> wrote:
> 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. c
On Thu, Nov 29, 2018 at 11:53 AM Pavlyk, Oleksandr <
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?
>
>
Current master is the 1.1
