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

Prepare Release-1.7 branches #24473

Closed
51 of 52 tasks
jacob-delgado opened this issue Jun 5, 2020 · 6 comments
Closed
51 of 52 tasks

Prepare Release-1.7 branches #24473

jacob-delgado opened this issue Jun 5, 2020 · 6 comments
Assignees
Milestone

Comments

@jacob-delgado
Copy link
Contributor

jacob-delgado commented Jun 5, 2020

This issue aims to track all steps needed to prepare the release 1.7 branches/builds.

Please add all steps taken here so we can document for future releases

@jacob-delgado jacob-delgado added this to the 1.7 milestone Jun 5, 2020
@jacob-delgado
Copy link
Contributor Author

See #22078 for the 1.6 release branch

@Mythra
Copy link
Contributor

Mythra commented Jul 21, 2020

FWIW for future release managers creating the branches can be done with:

REPOS=(istio pkg api proxy client-go tools common-files gogo-genproto release-builder)
ORGS=(istio)
for organization in "${ORGS[@]}"; do
  for repository in "${REPOS[@]}"; do
    export org=${organization}
    export repo=${repository}
    echo "Release for: [${org}/${repo}] ?"
    read -p "Do you wish to continue?" yn
    case $yn in
      [Yy]* ) true;;
      [Nn]* ) break;;
    esac
    git clone git@github.com:${org}/${repo}.git
    cd ${repo}
    git checkout -b release-1.7
    git push --set-upstream origin release-1.7
    read -p "Do you wish to continue?" yn
    cd ..
    case $yn in
      [Yy]* ) continue;;
      [Nn]* ) break;;
    esac
  done
done

This will go one by one, and let you stop both before and after cloning each so you can validate the branches are being created correctly.

@jwendell
Copy link
Member

There's an automation process being written for 1.8. It was planned for 1.7 but it didn't make it in time for today.

@ericvn
Copy link
Contributor

ericvn commented Jul 22, 2020

And as @jwendell noted, any comments about short-comings in the list above would be good (and update the list with comments). We will be looking at the list to do the automation.

@ericvn
Copy link
Contributor

ericvn commented Aug 11, 2020

Can we close this issue?

@jwendell
Copy link
Member

@ericvn We had kept this open because there's one issue that's still pending: istio/api#1551

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

No branches or pull requests

7 participants