-
Notifications
You must be signed in to change notification settings - Fork 63
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
Create an automated release workflow #338
Comments
On a related note, there exist some files in the repository that should not be committed accidentally contributors unless they are updating the base configuration (potentially as part of a version update). These files should be listed in
|
@a-sr mentioned: Gradle/Eclipse might have functionality for this. Python script exists for Kieler. |
This is the Python script for setting the version in Kieler: https://git.rtsys.informatik.uni-kiel.de/projects/KIELER/repos/semantics/browse/build/scripts/version.py |
A private |
I found out that OSGi does not allow versions like |
How does this look for an automatically generated change log? Note that the first couple links don't work because the release hasn't been tagged yet. I encourage everyone to have a careful look the log below and correct/improve any PR or issue titles that are unclear. We can also do a better job categorizing PRs by labeling them. Any PRs that should not be included can be marked as such add the Changelogv0.1.0 (2022-03-20)Summary: This is the first stable release of Lingua Franca. A number of new features have been introduced since v0.1.0-beta, including: generation of ROS2 nodes directly from LF code (C++); improved error handling; support for multiports and banks (TypeScript); modular support for runtime schedulers (C); and modal reactors (C and Python). Finally, a major refactoring has been performed in which all remaining Xtend code was ported to Java. Implemented enhancements:
Fixed bugs:
Closed issues:
Merged pull requests:
|
We should have a script that will make it easier to update our version numbers. Here are the relevant commits 18743fe db1602f that show the locations that have to be touched.
The script could take two arguments: the current version string and the new version string. The script should first perform a dry run and show all the changes. If the user confirms the changes are OK, commit them.
The text was updated successfully, but these errors were encountered: