You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The results computed with MOABB version 5.0 and earlier will be incompatible with version 6.0 and later because we changed many dataset names and codes (#448#455) and the sessions and runs naming scheme (#471 ).
How should we warn the users about that?
The text was updated successfully, but these errors were encountered:
Not an API break for me, as this concern the results of computation and not the code. Nonetheless, I agree that we should move to 1.0.0 version! This is time and we should allow users that want to keep their previous results to stick with 0.x versions
Next question is, since we will move to a new major version that allow API breaks, do we have some API to break? It will a good opportunity, next one could be in a long time! I'm thinking about changes in names or parameter names of functions (to keep homogeneity with other libraries). Maybe a good time to see if we have a better take on evaluation.process and evaluation.evaluate for example.
The results computed with MOABB version 5.0 and earlier will be incompatible with version 6.0 and later because we changed many dataset names and codes (#448 #455) and the sessions and runs naming scheme (#471 ).
How should we warn the users about that?
The text was updated successfully, but these errors were encountered: