Adjust release tools to always use the new patch release process
As part of extending the maintenance policy to account for three versions, the tooling associated with generating patch releases is compatible with two different scenarios:
- When no version is sent (e.g
/chatops run release prepare
) - This will trigger the new patch release process. - When a version is sent (e.g.
/chatops run release prepare 15.6.4
) - This will trigger the old patch release process.
As part of &968 (closed), we need to update release-tools to always use the new process regardless of the version.
This issue is for adjusting release-tools (and perhaps ChatOps?) to always perform releases for a single version using the new process. Once the /chatops run release prepare <version>
is trigger, it should
- Create a release/task issue using the new template
- Generate the corresponding blog post considering the merge request merged into the corresponding stable branch.