-
Notifications
You must be signed in to change notification settings - Fork 123
New release workflow #3566
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
base: master
Are you sure you want to change the base?
New release workflow #3566
Conversation
…_release_workflow
Added a TODO comment to indicate future MacOS support.
…into new_release_workflow
Andrewyx
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some feedback. src/software/tar-out/unix_full_system_tar.tar.gz should not be pushed to remote. Looks like some acceptance criteria may be missing, so please remember to refer to the issue specs
Andrewyx
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
nycrat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
On another note, perhaps it would be beneficial to build for previous macos versions as well? Obviously we can't build for every version but perhaps just some past major versions would work?

Description
New release workflow
Testing Done
Resolved Issues
#3554
#3567
Length Justification and Key Files to Review
Review Checklist
It is the reviewers responsibility to also make sure every item here has been covered
.hfile) should have a javadoc style comment at the start of them. For examples, see the functions defined inthunderbots/software/geom. Similarly, all classes should have an associated Javadoc comment explaining the purpose of the class.TODO(or similar) statements should either be completed or associated with a github issue