#Instructions

0) Before you start, copy from the template to the bottom of the file.  This keeps the previous release notes as well as the new ones.  New ones are at the bottom!
1) Do not touch any lines that start with #.
2) Insert content between the lines as needed.
3)  If nothing is needed, leave it blank, do not put in text such as No changes
3a) Always put something in the ECU summary line
4)  If a ticket or feature is testable / noticeable only at the ECU level (something like better bootloader compatibility), put it at the ECU level
5)  If something is testable at the ECU and domain level, put it at the domain level
6)  If something is testable at the ECU, domain, and vehicle level, put it at the vehicle level.

# For in-house ECU
7)  Put this in git in your ECU in \params\release_artifacts\release_notes.txt
8)  This should exist in the bootloader, app, and CAL and the changes should show up in the appropriate place.  (this is how we deal with variants...)

# For Supplier ECU
7)  Put this in your zip at the base level and call it release_notes.txt

#Release (MM.mm)
00.14
#ECU
##Summary
Always put something here
##New Features other than JIRA tickets
##Improvements other than JIRA tickets
##Known Issues
##Compatibility
#DOMAIN
##Summary
##New Features
##Improvements
##Known Issues
##Compatibility
#VEHICLE
##Summary
##New Features
##Improvements
##Known Issues
##Compatibility