-
Notifications
You must be signed in to change notification settings - Fork 30
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 SOMns v0.6.0 release #236
Comments
Java 10 just got release: http://jdk.java.net/10/ And, we probably want to update Truffle before the release, too. @Richard-Roberts what's your target date for a Moth release? |
I'm on no particular deadline to create a 0.1 release for Moth, but ideally, it's done before the end of March. Let's say April 01, which at least has some comical benefit. |
@Richard-Roberts @daumayr As it turns out updating Truffle is a major project, which I can't do myself at the moment. Are you aware of any issues that would require a more up to date Truffle/Graal? Problems with the new Truffle version I am aware of:
If there are no important reasons, I'll postpone the Truffle update, and release with the Truffle we got now. |
I don't have any issues with the current truffle/graal |
And that's it for 0.6.0: https://github.com/smarr/SOMns/releases/tag/v0.6.0 |
Thanks for all the fish! |
This is the issue to track the final tasks for the SOMns v0.6.0 release, which is tracked via the v0.6.0 milestone.
Extra Changes
master
torelease
to communicate more clearly how we use the master branch.update Truffle to latest version (don't do any changes that are not necessary, can be done later)Release Checklist
This list is supposed to make sure we do not forget any important steps during
release. It is based on https://github.com/smarr/SOMns/blob/dev/docs/release-checklist.md
1. Check and update issue tracker for issues associated with current milestone
2. Update CHANGELOG.md with all elements missing
A useful tool is the
github_changelog_generator
It can be used like this:
3. Make sure all desired changes are part of the
dev
branch.4. Prepare a release on GitHub with: https://github.com/smarr/SOMns/releases/new
The content is normally just the last part of the CHANGELOG.md
5. If everything looks good, tag the release using the GitHub feature
6. Push the commit that is tagged as release to the
release
branch.7. Announce the release
@daumayr @Richard-Roberts if you need something, anything, please chime in as soon as possible.
The text was updated successfully, but these errors were encountered: