Additions to 0.20 between RC and release #11948
Conversation
73e034e to
8e1e643
Compare
|
I don't understand why appveyor says " AppVeyor was unable to build non-mergeable pull request" while Github says "This branch has no conflicts with the base branch. Merging can be performed automatically." at the same time. |
|
I'm not sure either, but I did a big rebase to get rid of optics changes
and it may have got confused
…On Mon, 17 Sep 2018, 10:53 pm Olivier Grisel, ***@***.***> wrote:
I don't understand why appveyor says " AppVeyor was unable to build
non-mergeable pull request" while Github says "This branch has no conflicts
with the base branch. Merging can be performed automatically." at the same
time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11948 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEz6xmwgbMvCrlJ-xV0bvUTO9wVrkj0ks5ub5stgaJpZM4WSu5H>
.
|
|
do you want to try and update it? Should I? I don't think there's anything in the way of releasing right now. |
|
Does it make sense to cherry-pick #11945 ? These should probably be picked: There's no reason not to pick Rest looks good. Might just do that now and start building the wheels... |
|
Closing as superseded by #12151 |
This PR and branch are for tracking which commits from master are to be cherry-picked into 0.20 final, but missed rc1.