[Twisted-Python] Twisted Release Planning
Adi Roiban
adi at roiban.ro
Fri Jul 9 03:59:28 MDT 2021
On Fri, 9 Jul 2021 at 08:34, Tom Most <twm at freecog.net> wrote:
> 🌋
>
> Automating all this is a great project! Please feel free to ping me for
> reviews.
>
>
There is one blocker PR for the release as the newsfragment checks are
failing on the release branch... since the code is executed on the
to-be-merged on a branch named by GitHub Action something like
refs/pull/1617/merge
so the new fragment check fails to detect it as a release branch...as a
release branch should have a name starting with 'release-'
The PR is here. Any feedback will help to get this merge
https://github.com/twisted/twisted/pull/1617
This PR is important as I want to have a green release branch.
For the previous release, we just ignored the failure and did the release
anyway
But for this release I want it fixed :)
------------
This is also a non-blocker PR which contains a minor clarification for the
release process
https://github.com/twisted/twisted/pull/1616
--
Adi Roiban
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/twisted-python/attachments/20210709/39937f07/attachment.htm>
More information about the Twisted-Python
mailing list