Thanks for the feeback.
There is this ticket to update the release process after the migration. - #11621

It wasn't a priority as I felt there is no much interest into that.

I tried to push some dev doc changes in the past... but the changes were reviewed after 2 months of waiting in the queue...so it wasn't fun to work on this.

The regression report (I assume the equivalent is a GitHub label? Or is this no longer a thing?)

Yes. Is the regression label filter in GitHub Issues

More importantly, it talks about a branch naming convention tied to Trac issue numbers, which are no longer a thing.

The convenion is now tied to GitHub Issues

so the release branch for this should be release-22.2.01-12097

It's important for the branch name to be prefixed with release- as there is some automation triggered for these branches.

Second, I don't understand how pre-releases work. It seems like the docs suggest using a tag that matches the final version for the pre-release tag.

Third, there's no mention of tagging a final release, or what it should look like.

The pypi publish is triggered by creating a tag

see

twisted/.github/workflows/test.yaml

Lines 392 to 396 in 446ee13

    
           - name: Publish to PyPI - on tag 
        
             if: startsWith(github.ref, 'refs/tags/twisted-') 
        
             uses: pypa/gh-action-pypi-publish@v1.5.1 
        
             with: 
        
               password: ${{ secrets.PYPI_UPLOAD_TOKEN }}

And the tag is created using the GitHub Releases UI - https://github.com/twisted/twisted/releases/new

In the UI there is: Choose an existing tag, or create a new tag when you publish this release.

In the UI there is also the "Mark as pre-release" option

Does it make sense?

	- name: Publish to PyPI - on tag
	if: startsWith(github.ref, 'refs/tags/twisted-')
	uses: pypa/gh-action-pypi-publish@v1.5.1
	with:
	password: ${{ secrets.PYPI_UPLOAD_TOKEN }}