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.

Sign up for GitHub

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

Jump to bottom

Documentation: update how to cut Cilium releases #6616

Closed
ianvernon opened this issue Jan 11, 2019 · 5 comments · Fixed by #9496
Closed

Documentation: update how to cut Cilium releases #6616

ianvernon opened this issue Jan 11, 2019 · 5 comments · Fixed by #9496
Assignees
@ianvernon
Labels
area/documentation Impacts the documentation, including textual changes, sphinx, or other doc generation code.
Projects
Release Process
Milestone
1.7

Comments

@ianvernon
Copy link
Member

Update documentation for cutting releases to reflect that tags need to be pushed / images built, and then extract binaries from those images when using uploadrev.
@ianvernon ianvernon added the area/documentation Impacts the documentation, including textual changes, sphinx, or other doc generation code. label Jan 11, 2019
@ianvernon ianvernon self-assigned this Jan 11, 2019
@ianvernon
Copy link
Member Author

Note: old Cilium images for no longer maintained versions should be removed (e.g., v1.0, v1.1, v1.2) from the provision/pull-images.sh script in the packer-ci-build repo.

@ianvernon
Copy link
Member Author

Be sure to update Cilium tags in examples/getting-started/Vagrantfile (see #7298 )

@ianvernon
Copy link
Member Author

Close GitHub project and create new one for next release with specified columns

@ianvernon
Copy link
Member Author

Update stable tags for cilium, operator, docker-plugin

@ianvernon ianvernon added this to To do in Release Process via automation Apr 1, 2019
@ianvernon
Copy link
Member Author

Trigger ReadTheDocs build once release is published on GitHub

@ianvernon ianvernon added this to the 1.7 milestone Oct 24, 2019
@ianvernon ianvernon mentioned this issue Oct 24, 2019
Merged
Release Process automation moved this from To do to Done Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ianvernon ianvernon

Labels
area/documentation Impacts the documentation, including textual changes, sphinx, or other doc generation code.
Projects
No open projects
Release Process
  
Done
Milestone
1.7
Development

Successfully merging a pull request may close this issue.

Documentation: update release guide cilium/cilium
1 participant
@ianvernon