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
@Ompragash@rooftopcellist I realize that there's a lot of the releasing process that isn't written down publicly (or at least nowhere I know). Where should we collect such information, including who does the various steps? Some things (like preparing the next major release by creating the corresponding folder etc.) can easily be done by community folks, some others (like doing the actual release) can only be done by you (since we cannot publish to the ansible PyPi).
Thanks for bringing this up @felixfontein :)
I wasn't aware of this but will document it and the other steps that are involved to build the tarball and send a PR!
Glad to see this getting noted in the release process. Our automation already notifies us of any new major versions that need manual addition, but keeping this as part of the release process will be great!
We should update the data at endoflife.date on https://github.com/endoflife-date/endoflife.date/blob/master/products/ansible.md once we release a new major version, and also once a major version is End of Life (change
eol: false
toeol: <ISO-Date>
for that major release train).@Ompragash @rooftopcellist I realize that there's a lot of the releasing process that isn't written down publicly (or at least nowhere I know). Where should we collect such information, including who does the various steps? Some things (like preparing the next major release by creating the corresponding folder etc.) can easily be done by community folks, some others (like doing the actual release) can only be done by you (since we cannot publish to the ansible PyPi).
Ref: endoflife-date/endoflife.date#1047 (comment)
The text was updated successfully, but these errors were encountered: