Release etc

[larsoner]

Some TODO items, though I'm sure there are plenty:

• Cut a release on GH (used a tag, okay)
• Download artifacts from release.yml run and manually make a PyPI release (first release must be done manually to create the PyPI namespace AFAIK)
• Add @larsoner and @drammock as maintainers on PyPI, we can add you to mne-tools PyPI org
• configure trusted publishing on PyPI
• Add to mne-python tools/circleci_dependencies.sh doc/sphinxext/related_software.txt so that it renders properly as related software: MAINT: Add mne-denoise to CI dependencies mne-python#13607
• Add to conda-forge using grayskull: Add mne-denoise recipe conda-forge/staged-recipes#31994
• Add to https://github.com/mne-tools/mne-installers

Feel free to add/remove/edit as needed, these are just some items that occurred to me as good steps once you're ready to cut a 0.1 or 1.0 or whatever

[drammock]

manually make a PyPI release (first release must be done manually to create the PyPI namespace AFAIK)

the pypi release should live under the MNE org. Org owners (me and @larsoner) can create empty projects through the PyPI interface. I think that means that we could:

1. create the empty project
2. create a PyPI org team to manage that project
3. (optional) add @snesmaeili and @BabaSanfour to that team (you'll need PyPI accounts if you don't already have them)

I say step 3 is optional because we'll want to set up a trusted publisher action anyway, so that pushes to PyPI happen automatically when release tags are made, which means there's actually very little to be done in interacting with PyPI directly. Off the top of my head, the main thing you could do and might want/need to do would be to yank a release if it were security-flawed somehow... which for scientific software like this is pretty rare.

[larsoner]

Add to mne-python tools/circleci_dependencies.sh so that it renders properly as related software

Sorry about this part it's outdated, should say docs/sphinxext/related_software.txt because we restructured where we put the related software...

[larsoner]

Trusted publishing configured!

[BabaSanfour]

oh I should have checked before going with it! Fixed. Also I added to conda and installers just waiting for them to merge and tests should pass on installers.

finally, for codecov, does mne-tools have an org under which we can add mne-denoise ?

[larsoner]

finally, for codecov, does mne-tools have an org under which we can add mne-denoise ?

Done, configured / added this repo

[BabaSanfour]

Perfect, configs done. should be start working from the next push. I think only conda recipes is left now.