Currently, flex releases are manual. This takes time and is error prone.
We would like for release tags to trigger flex releases.
Such a system needs to:
- build the flex release archives.
- generate release notes based on the NEWS file.
- notify the flex-announce mailing list (NB it is ok if that email needs approval).
- increment the recorded current and previous version numbers of flex based on the release number from the release tag and what flex's version numbering is recorded as.
When we have that, it will be possible to release flex whenever an important fix or feature change appears on master or when sufficient time has passed since the previous release.
Currently, flex releases are manual. This takes time and is error prone.
We would like for release tags to trigger flex releases.
Such a system needs to:
When we have that, it will be possible to release flex whenever an important fix or feature change appears on master or when sufficient time has passed since the previous release.