Currently we are supporting an official and stable release of the tooling and 2 pre-releases: 1) https://github.com/ipa320/ros-model/releases/tag/1.5.0_prerelease which contains the long-term version of the grammars 2) https://github.com/ipa320/ros-model/releases/tag/1.4.0_TestComponentStacks which introduces the concept of component stacks, see https://github.com/ipa320/ros-model/pull/116#issue-540977226 for further information An updated version of 1 is now the master version of the repository (see https://github.com/ipa320/ros-model/pull/132). I think that the most efficient strategy to proceed now is: - [x] Complete the ROS2 support (at least a minimum one) which pass by continue the work started in https://github.com/ipa320/ros-model/pull/131 and https://github.com/ipa320/ros-model/pull/130 - [x] Merge to master the ROS2 support - [x] Release master branch as 1.5.0 --> Plan mid-June The next release should integrate the changes of the pre-release 2: - [x] consolidate the PR https://github.com/ipa320/ros-model/pull/116 at least the validators and the launch files generators will have to be updated (draft https://github.com/ipa320/ros-model/pull/116/commits/5aa201910d338fd0cda03db83f851e94758b2ede). The branch - [x] Rebase to the master version - [x] Merge to master - [x] Release master branch as 1.6.0 --> Plan end of August
Currently we are supporting an official and stable release of the tooling and 2 pre-releases:
An updated version of 1 is now the master version of the repository (see #132).
I think that the most efficient strategy to proceed now is:
--> Plan mid-June
The next release should integrate the changes of the pre-release 2:
--> Plan end of August