Ralph,
On the ompi-release repo, developers with no write permissions (e.g. all
but RM, GK and admin) cannot set label nor milestone nor assign PR. The bot
was a creative way to work around this limitation.
IIRC, the bot does not accept instructions from non Open MPI developers.
The new "review"
We talked about this on the call today.
SHORT VERSION
=
I'll merge ompi and ompi-release in the very near future (next 48 hours). Any
PRs still open on the ompi-release repo will need to be re-opened on the ompi
repo by their respective authors.
MORE DETAIL
===
The ompi-a
All the branches from ompi-release have now been merged back into the ompi repo.
(amusingly, we all got a gitdub email for the creation of each old release
branch)
The ompi-release repo is now effectively closed. It will not be deleted,
however, so that old links won't go stale, and old conver
Jeff,
in order to re-create a PR that i hope is merged before v2.0.2, what
shall i do ?
- one PR vs the v2.0.x branch ?
- one PR vs the v2.x branch ?
- two PRs vs the v2.0.x and v2.x branches ?
Cheers,
Gilles
On 9/21/2016 10:20 AM, Jeff Squyres (jsquyres) wrote:
All the branches from
On Sep 20, 2016, at 9:40 PM, Gilles Gouaillardet wrote:
>
> in order to re-create a PR that i hope is merged before v2.0.2, what shall i
> do ?
>
> - one PR vs the v2.0.x branch ?
>
> - one PR vs the v2.x branch ?
>
> - two PRs vs the v2.0.x and v2.x branches ?
Yes, now that we have a v2.0.x