|
|
# Release Process
|
|
|
|
|
|
* Time based releases - Every 3rd Thursday of month
|
|
|
* Get feedback from Support before tagging the release
|
|
|
* Try generating CHANGES file from git log
|
|
|
* Clearly state "urgency" for each release
|
|
|
* ESV - two years bugfixes + two years security-only (when next ESV is out)
|
|
|
|
|
|
# Development Process
|
|
|
|
|
|
* Attach milestone to MRs
|
|
|
* Do more documentation / discussion on the tickets
|
|
|
* Update the website with release notes automatically
|
|
|
* Put CVE number in the title
|
|
|
* Be more precise when writing the issue and MR subjects
|
|
|
* Add milestone to all replay merges |