Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

17.06.0 RC3 tracker #8

Closed
40 tasks done
andrewhsu opened this issue Jun 6, 2017 · 30 comments
Closed
40 tasks done

17.06.0 RC3 tracker #8

andrewhsu opened this issue Jun 6, 2017 · 30 comments

Comments

@andrewhsu
Copy link
Contributor

andrewhsu commented Jun 6, 2017

STATUS: completed merge list for RC3

@andrewhsu andrewhsu mentioned this issue Jun 6, 2017
23 tasks
@cyli
Copy link

cyli commented Jun 6, 2017

moby/moby#33464 p1 - @cyli to confirm

Yes, p1

@cyli
Copy link

cyli commented Jun 6, 2017

Also, the following two swarmkit PRS have been cherry-picked into the swarmkit 17.06 branch already and should also be in rc3:

Update: apologies, I was looking at the wrong branch - that has already made it into rc2 - thanks!

@mlaventure
Copy link

would add moby/moby#33456 as a p1

@thaJeztah
Copy link
Member

I think there were a couple of PRs left as comment that were not yet added to the checkbox list

@ybalt
Copy link

ybalt commented Jun 7, 2017

Hi guys, can you please take a look at issue #32195 mentioned by vovimayhem, as it really a showstopper for many people

@skinofstars
Copy link

skinofstars commented Jun 7, 2017

Please consider including docker/cli#150 as it's breaking swarm stack deploy on current release of Mac (17.06) with Cloud (17.05)

@kinghuang
Copy link

For docker/cli#150, @vdemeester has a PR at docker/cli#162.

@thaJeztah
Copy link
Member

Adding moby/moby#33577, which reverts a breaking change in RunC

@thaJeztah
Copy link
Member

Ok, I just went through all the comments on the old issue, checked if they were included in the old issue checklist, then checked if they were included in this issue checklist, and looks like the following suggested PR's / issues didn't make it from the old to the new issue.

(I think we should stick to using a single issue, because this is quite time-consuming, and easy to lose track)

@thaJeztah
Copy link
Member

This one should also be added /cc @Madhu moby/moby#33555 (or a separate PR against docker-ce)

@andrewhsu
Copy link
Contributor Author

andrewhsu commented Jun 7, 2017

@thaJeztah i've added your list to the backlog section (with some simple editing to shorten the line) so it can get a priority and then move up into the cherry-pick pr list as appropriate, thanks for consolidating

@cyli
Copy link

cyli commented Jun 7, 2017

@andrewhsu Can moby/swarmkit#2210 be moved off the backlog because it was merged into the 17.06 branch already? (docker-archive/docker-ce@0efdcc4)

@aaronlehmann
Copy link

Sending SIGUSR1 to the docker daemon can crash it. This issue has been showing up in the field. moby/moby#33598 should fix it.

@cyli
Copy link

cyli commented Jun 8, 2017

(have opened docker-archive/docker-ce#43 for the swarmkit cherry-picks)

@nishanttotla
Copy link

I've opened docker-archive/docker-ce#44 to include cherry-picks related to digest pinning for docker stack deploy (docker/cli#121)

@andrewhsu
Copy link
Contributor Author

I've updated the list at the top from all comments in this issue thus far. Identified some of the trickier PRs that will need to be created for libnetwork vendoring (with help from @tiborvass ). Need help on prioritization @mavenugo and there seems to be some unfinished issues still open.

@thaJeztah
Copy link
Member

docker/cli#143 should be included; it's a deprecation that was postponed already a few times

@thaJeztah
Copy link
Member

@mavenugo tentatively adding moby/moby#33609, which was not backported to master, but is part of 1.13 / 17.03, and fixes a possible panic (but please verify)

@mavenugo
Copy link

mavenugo commented Jun 9, 2017

@thaJeztah Good catch and agreed. I will spend some time this morning to review the pending PRs in the list.

@aaronlehmann
Copy link

Let's also include moby/swarmkit#2233. This fixes a crash bug.

@aaronlehmann
Copy link

Nominating moby/swarmkit#2237, which is related to a defect in the allocator that causes it to assign duplicate IPs.

@thaJeztah
Copy link
Member

@mavenugo @andrewhsu @aaronlehmann we need moby/moby#33629 as well; the deprecation plan was to disable v1 registries by default in 17.06, so that users have enough time to migrate their legacy registries in time for support them being removed in v17.12

@mavenugo
Copy link

@aaronlehmann moby/swarmkit#2233 is cherry-picked. Once moby/swarmkit#2237 is in swarmkit master, can you pls chery-pick into swarmkit 1706 bump branch and open a PR in docker-ce ?

I added this PR to the tracking list above.

@vdemeester
Copy link

@mavenugo docker/cli#180 should be included too (fixing in docker/cli#182)

@cyli
Copy link

cyli commented Jun 12, 2017

I'd also like to include: moby/swarmkit#2234 and moby/swarmkit#2238, since they help resolve edge cases when there's a demotion during CA rotation.

@aaronlehmann
Copy link

I've opened docker-archive/docker-ce#67 for moby/swarmkit#2237.

@cyli could you please cherry-pick those two fixes, then I'll update docker-archive/docker-ce#67 ?

@thaJeztah
Copy link
Member

moby/moby#33472 was merged, so should be ready for cherry-picking if we want it

@unclejack
Copy link

Is there something I could do to make sure moby/moby#33472 gets cherry-picked for the release?

@aaronlehmann
Copy link

I know RC3 is already out, but I don't know where else to track this (I agree with @thaJeztah that having a separate issue for each RC is a little tough).

I opened docker-archive/docker-ce#75 for moby/swarmkit#2244.

@andrewhsu
Copy link
Contributor Author

I've moved the backlog to a new issue for tracking 17.06.0 RC4: #14

@aaronlehmann @thaJeztah having a new issue for each RC helps me in managing a smaller list of PRs. Plus, the ticket that is referenced by the tracking issue says the RC release it is tracked in. Willing to discuss a better procedure or use of a better tool to track issues across different repos for the 17.07 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests