Skip to content
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

Version 2.2 Release #261

Closed
26 tasks done
ryanhammonds opened this issue May 3, 2021 · 6 comments
Closed
26 tasks done

Version 2.2 Release #261

ryanhammonds opened this issue May 3, 2021 · 6 comments
Labels
2.2 Updates to go into a 2.2.0 release

Comments

@ryanhammonds
Copy link
Member

ryanhammonds commented May 3, 2021

I've aggregate/organized the changes since the last release to help with the 2.2 changelog and to track what's left to be done before the next release.

@TomDonoghue feel free to change this as you see fit. I think wrapping up open PRs marks a good target to release 2.2, but feel free to add additional to-dos here.

Aperiodic

Simulation

Plotting

Maintenance

Documentation

@TomDonoghue
Copy link
Member

This looks great, thanks for doing this @ryanhammonds!

I don't we want to add anything beyond the current open PRs for 2.2, as soon as we get the open things merged we can do a new release.

@ryanhammonds
Copy link
Member Author

Hi @TomDonoghue, I caught up today on all the open PRs and they should be ready to go. I'll wait to merge the open PRs until you get a chance to approve them too. We've both already reviewed them so hopefully it won't be too much work. After that, I'll start preparing a new release!

@TomDonoghue TomDonoghue added the 2.2 Updates to go into a 2.2.0 release label Aug 30, 2021
@ryanhammonds
Copy link
Member Author

ryanhammonds commented Sep 15, 2022

Hi @TomDonoghue, what do you think about removing #235 from 2.2 and getting a release out soon? I was going to release a new bycycle version but noticed it requires neurodsp 2.2 and it seems better to release with a neurodsp pypi dependency rather than a link to the main branch.

@TomDonoghue
Copy link
Member

@ryanhammonds - yes, I think that is a good idea! We should just get a new release out at this point, and there's no reason not to move #235 into a 2.3 release! Sorry for dropping off on working on the remaining PRs to get the release out!

The last open questions then seems to be whether there are things in #275, #277, and #303 that should be prioritized into 2.2. I think #277 can merge in quick, but the other two seem to have some open questions - can you do an a quick status check and see what you think should happen with them? If you tag me in, I'll do my best to help with anything over the next few days.

@ryanhammonds
Copy link
Member Author

Yeah, I think #277 can be merged as is. #275 and #303 are smaller bugs / edge cases that can wait until 2.3 or maybe a smaller minor update (2.2.1).

So I can merge #277 (lmk if you want to check over it first) and then go ahead and release if that sounds good to you?

@TomDonoghue
Copy link
Member

This sounds like a good plan to me! I agree that #275 and #303 are minor enough points to be merged into a future release.

I had a quick check of #277, and that looks good to merge!

There is also #299 open, which most notably adds the 'aperiodic' module to the list of sub-modules. When you are ready to release, can you have a quick check for anything else worth adding into the readme, and then merge that?

Also, also - it crossed my mind that testing against 3.10 should now be supported from Github actions, so I have added that in #307. As long as that looks good to you, do you want to merge that in as well, and then 2.2 officially supports 3.10?

Otherwise I think we are ready for a new release - are you good to go with that after merging these last things in? Other than using this issue to list the updates on release page, I think it should be a normal release! Let me know if you need anything else from me - but there's nothing else I want to check in on, so also feel free to just go for it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.2 Updates to go into a 2.2.0 release
Projects
None yet
Development

No branches or pull requests

2 participants