You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To better document the new releases, we should add and maintain a releases notes/change log document to the repo.
As I worked a bit with the multi-file structure of the release notes in YARP ( https://github.com/robotology/yarp/tree/master/doc/release ) and iDynTree ( https://github.com/robotology/idyntree/tree/master/doc/releases ), I think that having a separate file for each release add quite a bit of overhead for each release, especially if the release is done via the the GitHub's web interface. For this reason, for this repo I would like to try to use a single document for all the release notes, with different section for each release, something like what is documented in https://keepachangelog.com/en/1.0.0/ .
The text was updated successfully, but these errors were encountered:
Add the yarpConfigurationString to configure the YARP plugins with a single yarpConfigurationString embedded in the SDF code of the plugin (Add <yarpConfigurationString> parameter #396).
To better document the new releases, we should add and maintain a releases notes/change log document to the repo.
As I worked a bit with the multi-file structure of the release notes in YARP ( https://github.com/robotology/yarp/tree/master/doc/release ) and iDynTree ( https://github.com/robotology/idyntree/tree/master/doc/releases ), I think that having a separate file for each release add quite a bit of overhead for each release, especially if the release is done via the the GitHub's web interface. For this reason, for this repo I would like to try to use a single document for all the release notes, with different section for each release, something like what is documented in https://keepachangelog.com/en/1.0.0/ .
The text was updated successfully, but these errors were encountered: