Closed JuliaKukulies closed 9 months ago
Do we want to include #362 #361 in 1.5.2? Happy either way...
Edit - meant #361, #362 needs some more discussion.
I also think we should do #347 before release
Agreed, I think we can figure out these three PRs/issues before the next release. Added that to the check list!
Hej all, could "Adding checklists for the issue tracker" #358 be considered as part of the v1.5.2 release? @fziegner has nearly finished this PR.
I further added "Introducing pylint in our workflow" #278 to the milestone list for v1.5.2. This work is also more than ready ;-)
Hej all, could "Adding checklists for the issue tracker" #358 be considered as part of the v1.5.2 release? @fziegner has nearly finished this PR.
We can also merge directly into main
outside of a release, but I'm happy to get it in for v1.5.2 as well. Let me know when it's ready and I'll provide a review :)
Great, @fziegner and @fsenf ! I will have a look at the PR to my fork today and if #358 is ready, happy to provide a review and convert it into a real PR.
I would say if it takes longer than the other remaining issues for v1.5.2, we can directly merge to main
after the release to not further postpone the release since these changes only concern our internal workflow. But since this looks quite ready, Id say we can include it in v1.5.2 :)
Version number, changelog and notebooks updates in #381
Well, that ended up being mildly painful, but v1.5.2 is now live 🎉
We are almost ready for the next release. Here is the checklist: