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

Move release-1.2 forward to 3d58b9c07fdd2bf8cb063c30d791b94649b794e5 #22710

Merged
merged 245 commits into from
Mar 9, 2016

Conversation

eparis
Copy link
Contributor

@eparis eparis commented Mar 8, 2016

however this excludes PR #22430

gswallow and others added 30 commits February 9, 2016 16:35
for vsphere provider docker currently only supports 1.9.1 release.
The older versions of docker are failing on jessie due to issue moby/moby#18793
and newer version 1.10.x is not properly tested.
All AWS errors should be wrapped in a user-friendly error before
returning.
Configurations in config-default.sh should take default values if they
are set outside of the script. `roles` option is an exception. This
patch fix it to maintain consistency behavior with other options.
…w gcr

image consistent with the code base.
Change the label on the daemonset to 'app'.
@k8s-github-robot k8s-github-robot added kind/old-docs size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. labels Mar 8, 2016
@bgrant0607 bgrant0607 assigned bgrant0607 and unassigned j3ffml Mar 8, 2016
@bgrant0607 bgrant0607 added this to the v1.2 milestone Mar 8, 2016
@bgrant0607
Copy link
Member

cc @david-mcmahon

@bgrant0607 bgrant0607 mentioned this pull request Mar 8, 2016
@eparis
Copy link
Contributor Author

eparis commented Mar 8, 2016

I'm trying to figure out how to get a diffstat without the (obvious) docs nonsense... We'll see....

@bgrant0607
Copy link
Member

The diff of the PR I wanted to exclude is at the bottom. At a glance, the rest looks like doc-munging-related changes.

@k8s-bot
Copy link

k8s-bot commented Mar 8, 2016

GCE e2e build/test passed for commit 3eb6278.

@eparis
Copy link
Contributor Author

eparis commented Mar 8, 2016

Diff from this PR to upstream master (3d58b9c)

https://gist.github.com/eparis/591788686969412309e4

This diff ignores all changes to files which end in .md
This diff ignores all changes which include the words 'releases.k8s.io'

This is the rest....

@eparis
Copy link
Contributor Author

eparis commented Mar 8, 2016

I got that diff by adding the following to my .git/config

[diff]
    tool = eparis-diff
[difftool "eparis-diff"]
    cmd = /tmp/diff.sh $LOCAL $REMOTE

And then putting the following in /tmp/diff.sh

#!/bin/bash

LOCAL="$1"
REMOTE="$2"

if [[ $LOCAL == *".md" ]]; then
    exit
fi

diff -Naup -I 'releases.k8s.io' "${LOCAL}" "${REMOTE}"

And running:

git difftool -y 3eb6278653c09c9f99f13f31fbdcaf1984dca65f..3d58b9c07fdd2bf8cb063c30d791b94649b794e5

So now you can reproduce my results at home!

(I am assuming that everyone will have my commit in their tree, in case you don't and are interested...)

I have

[remote "upstream"]
    url = https://github.com/kubernetes/kubernetes
    pushurl = crap
    fetch = +refs/heads/*:refs/remotes/upstream/*
    fetch = +refs/pull/*/head:refs/remotes/upstream/pr/*

So all I have to do is

git remote update
git show upstream/pr/22710
  or
git show 3eb6278653c09c9f99f13f31fbdcaf1984dca65f

@bgrant0607
Copy link
Member

Awesome. LGTM

@bgrant0607 bgrant0607 added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 8, 2016
@bgrant0607
Copy link
Member

cc @roberthbailey

@david-mcmahon
Copy link
Contributor

Can we include the reproduction steps here for history's sake? In case we need to do something like this in the future. Commands with comments, please.

@eparis
Copy link
Contributor Author

eparis commented Mar 8, 2016

Notice this does not 'rewrite' history, it does not leave a vestigial tag, it just marches the release-1.2 branch forward. I hope people won't need to do this often. A wholesale update like this just doesn't belong. But basically what happened was the bgrant reviewed every PR between the release-1.2 branch (4d599ea) and master (3d58b9c) he indicated every commit between those 2 points was reasonable for 1.2 except possibly #22430. So I found the first commit before the problematic PR. That first commit was 7e9256b.

So my basic steps (with a bit of pseudo-code)

// create my local release-1.2 branch
- git checkout -b release-1.2 upstream/release-1.2

// Merge everything in master that we know is good into the release-1.2 branch
// but automatically solve conflicts by taking 'their' changes.
- git merge 7e9256b39 -X theirs

// Get all of the merges that I didn't get from the merge
- git log --merges 7e9256b39..3d58b9c07fdd2b --oneline --reverse
        a6aaf81 Merge pull request #22430 from gmarek/round-robin
        1c6a6aa Merge pull request #22697 from eparis/docs-readme-link
        43aa3d3 Merge pull request #18338 from gmarek/register-kubelet
        75699ff Merge pull request #22458 from bprashanth/ing_tls_e2e
        3d58b9c Merge pull request #22678 from spxtr/feature-tests

// For each merge I need to cherry-pick. We know that parent #1 of each merge is the 'trunk'
// so that helps. I do this for all of the above EXCEPT a6aaf81
- git cherry-pick -m 1 $SHA

// Sadly a 1c6a6aa touches docs and so does the release branch, so it had a conflict.
- git status // to see what files were a problem
- vim + filenames to fix the problems
- git add $filenames
- git commit

// Now we've got all the code we need but most likely the -X theirs merge strategy screwed up the docs. So we re-run
- build/versionize-docs.sh

// Then we push it and open the PR and feel really smug.
- git push eparis release-1.2:release-1.2

@bgrant0607
Copy link
Member

Merging.

bgrant0607 added a commit that referenced this pull request Mar 9, 2016
@bgrant0607 bgrant0607 merged commit e9a3ef2 into kubernetes:release-1.2 Mar 9, 2016
shyamjvs pushed a commit to shyamjvs/kubernetes that referenced this pull request Dec 1, 2016
shouhong pushed a commit to shouhong/kubernetes that referenced this pull request Feb 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/design Categorizes issue or PR as related to design. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.