-
-
Notifications
You must be signed in to change notification settings - Fork 49
Tag new release? #75
Comments
I think the idea was to tag a new release after the merge of the new R-K solver, maybe it was just forgotten? |
The question is if we should tag it as v"0.3.0" or v"0.2.1" (v"0.2.0" points to the old implementation)? |
The new solvers have changed the api, right? Then I think |
I think they haven't. For example, Mauro had to put in some effort to support those "scalar-like types" as we had them before. |
The interface of the low-level function changed somewhat:
vs before
For the exported functions this only adds |
@mauro3 : I just added the export of If there are no objections I will tag the current master as v"0.2.1" instead of v"0.3.0" since the API hasn't really changed. |
Yep, that sounds good. |
Is the tagging happenning? Would be nice to get rid of those annoy deprecation warnings... |
Given #76 (comment) I just went ahead and tagged 0.2.1 |
Thanks |
Is it possible to tag a new release for this project? I've been using the new Runge-Kutta solver (particularly with the keyword arguments support), and it would help to have a version I can specify in my REQUIRE. Thanks.
The text was updated successfully, but these errors were encountered: