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

Bump firecracker version to v1.0.0 #382

Closed
7 tasks done
github-actions bot opened this issue Feb 4, 2022 · 4 comments
Closed
7 tasks done

Bump firecracker version to v1.0.0 #382

github-actions bot opened this issue Feb 4, 2022 · 4 comments
Assignees
@Callisto13
Labels
area/dependency Issues or PRs related to dependency changes area/firecracker Indicates an issue or PR related to Firecracker kind/feature New feature or request priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2022 •
edited by Callisto13
Loading

This is an automatically generated Issue to bump the version of firecracker
in our tests. There are some manual steps to get new releases of our fork
branch published.
This Issue is to track those manual steps.

To complete work on this Issue:

  • Update (merge or rebase) the fork macvtap feature branch to the latest upstream release tag v1.0.0. Note: Do not update the feature branch to upstream main.
  • Make sure it builds. (See: doc)
  • Push the updated firecracker 'feature/macvtap' fork branch.
  • Create a new tag on the updated firecracker 'feature/macvtap' fork branch: git tag -s v1.0.0-macvtap -m v1.0.0-macvtap.
  • Push the tag to the fork: git push <remote> v1.0.0-macvtap (A new release will be created.)
  • In this repo, trigger the nightly_e2e workflow
  • Once the tests have passed you can close the Issue, if the tests fail, either fix them or roll back the version

Auto-generated by issue-bot.
@github-actions github-actions bot added area/dependency Issues or PRs related to dependency changes area/firecracker Indicates an issue or PR related to Firecracker kind/feature New feature or request labels Feb 4, 2022
@Callisto13 Callisto13 added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Feb 4, 2022
@Callisto13
Copy link
Member

Blocked on #384

@Callisto13 Callisto13 mentioned this issue Feb 4, 2022
Merged
@yitsushi
Copy link
Contributor

yitsushi commented Feb 7, 2022

#385 is merged, I think this one is not blocked anymore.

@Callisto13
Copy link
Member

sweet, when the e2es pass we can close this

@Callisto13
Copy link
Member

kicked them off just now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Callisto13 Callisto13

Labels
area/dependency Issues or PRs related to dependency changes area/firecracker Indicates an issue or PR related to Firecracker kind/feature New feature or request priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@yitsushi @richardcase @jmickey @Callisto13