Open scott-huberty opened 1 month ago
Sure. Not all open issues are associated with a release. Maybe we should go through those that are not associated and attach them to a tentative release? It can be .3 or later if you don't want to include them in .2... and we can adjust these down the road... but having them labeled may help provide clarity about the objectives of the forthcoming releases.
Sure! I recently assigned some to .3, but feel free to swap tickets between .3 and .2 as you see fit.
There have been a number of bug fixes and enhancements since the initial release, so I think now is a good time to cut a new release.
I've started a project tracker. I'm thinking September 1st is a generous timeline. I'm also going to be processing some data in August and so I will take the opportunity to look out for anything that should be improved. @christian-oreilly does this sound reasonable to you?EDIT: I forgot, we already have a project tracker for .2. I deleted the new one that I created.