-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MAINT: Release? #85
Comments
Sure I was originally going to wait for #73 to get sorted out, but if it's a blockage for MNE-Python, we can do so now. I just follow the mne-bids release process :p. Is that sufficient? |
Yeah it would be good to push one out, mne-bids process should be fine! |
Friendly ping, @adam2392 do you think you could do this within the next few days? No worries if you can't, but it would be great if we could include |
Sorry I'm in vacation with my family. Coming back tonight and will try to slate a release then. |
Amazing, thank you! Enjoy the rest of your vacation 🏝 |
I just made a release. @hoechenberger and @larsoner |
@adam2392 are you up for cutting a new release of mne-connectivity? That would make it easier to include it in the standalone installer for MNE-Python.
Or if you have a release process you generally follow documented somewhere, I could take a stab at it. Or if it's not documented, I can also do it if the process is just 1) change version, commit, push; 2) release on Github; 3) push to PyPi; 4) push to maint/0.3; 5) change version to next dev and push.
The text was updated successfully, but these errors were encountered: