backport: 1.6.2 backport patches#173
Conversation
…5-fix-link [stable-1.5]docs: Update architecture doc URL (cherry picked from commit 88715c4) Fixes: kata-containers#171 Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
|
I see quite a lot linter issues. |
…vis-go-version travis: Update go version on travis (cherry picked from commit c99869a) Fixes: kata-containers#168. Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
…nter-change lint: Switch golang linter to golangci-lint (cherry picked from commit e2b4377) Fixes kata-containers#156 Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
|
/test |
jodh-intel
left a comment
There was a problem hiding this comment.
How are you creating the commits? I do find the "Merge pull request" text a bit confusing as they look like merge commits. The process to follow is documented in https://github.com/kata-containers/community/blob/master/Backport-Guide.md.
|
@jodh-intel i cherry-picked them using |
|
@ganeshmaharaj - Let's not worry this time round. But, yes, the doc is supposed to define the process we use. That said, feel free to raise issues/PRs if you think it should change. I also wonder if we could automate more of the backport work to make the results more consistent (and the doc smaller! ;) |
|
I know a number of upstream (kernel) maintainers have scripts they use to help automate the backporting. I wonder if any of those are available and suitable (or adaptable)... |
Backport includes below changes.
#172
#169
#155