Closed jcoliz closed 2 years ago
Also will be included in this release
👍
And...
Hi @jcoliz! Thanks a lot for stepping in and updating and cleaning up everything! Even though i don't have much time to actually contribute happy to help if you have any questions!
Thanks for checking in, @luajalla. I appreciate the kind words. Everything will be wrapped up when this release concludes (it will be 3.1.0 now, because of new API). The one thing that would be helpful is if you have any opinions or insight on #31 . Anything you could write up there to describe the problem, or what approaches are to be considered, that would be stellar.
Closed by #64. With the addition of new functions, a minor version bump is warranted. So will be 3.1.0.
This issue tracks Release 3.0.1.
My thought here is that we should get 3.0.0 out into the wild with ONLY the netcore framework change, rather than release framework changes and bug fixes in the same go. Once we get some uptake on 3.0.0 to ensure all is well, then 3.0.1 should go out with bug fixes.
The following issues have tested fixes waiting in feature branches. This will clean out the issues list of all known bugs.
22
27
13