Suggested update to git workflow

[konglobemeralt]

As a final step when finishing a pull request, the feature/bugfix/enhancement should be added to the release draft document. Look at the drafts "Trigger and action" or the draft for more info.

For example, a trigger and action release had we followed this might have looked like this:

TRIGGER AND ACTION RELEASE

Maestro is now able to send basic trigger and action messages enabling a test object to execute predefined actions when specific conditions have been met.

This release is compatible with Maestro Tools x.x.x and Util x.x.x

New Features 🚀

Trigger and Action

• #111 Trigger and action file parser. ScenarioControl module can read a trigger and action config file.

• #109 Break detection algorithm. ScenarioControl can detect if a test object is braking based on MONR.

• #101 C-ITS reads EXAC and ACCM. C-ITS control can now read two trigger and action messages from the message queue.

• #90 Trigger Class. A trigger class containing all functionality expected from a trigger.

RVSS and Data Dictionary

• #72 RVSS and data dictionary. Everything related to RVSS and dataDictionary

Bug Fixes 🐛

• #119 Uploads now working. Trajectory files uploaded to the server got appended with TCP messages at the end of file. No longer an issue.

Improvements 👍

• #110 Generalised file locations.. The location for all files necessary to run the server can now be defined. Defaults to ~/.maestro

Other Changes

• Version number structure has been updated. Instead of MASTER:DEV:ITERATION format from before we are now using MAJOR:MINOR:PATCH

Issues 💥

• #1 Link to issue Server spontaneously combusts.

[LukasWikander]

Perfect! Might be a good idea to let everyone review this though.

[LukasWikander]

Also, I know @viktorjo is looking at collecting all our repos in some sort of "project", so it might be nice to have this workflow document there instead.

[konglobemeralt]

@viktorjo Have you checked this? Did it work to organise everything into a "project" here on github?