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
Classification metrics become task specific since 0.10, meaning use shall import <Task><Metric> or set a task in Metric(task=<task>) which resolved much confusion of automatic task estimation. Also, the 0.10 set this task as optional, so it still supports leaving the decision to TM. In 0.11, we have set this task argument as required, which would break many naive users' use cases and prevent them from upgrading to the latest
Motivation
Just thinking as we made this breaking change in 0.11 with the making task required, and the next will be 1.0, so to re-release all from the 0.11 series with post (so, for example, 0.11.2.post1)
so all will be rereleased
0.11.0.post1
0.11.1.post1
0.11.2.post1
0.11.3.post1
0.11.4.post1
Pitch
When we allow not passing task and hold this friction for 1.0 so, it will also be easier to communicate and for a user to decide if he stays below 1.0 or after...
Alternatives
Additional context
The text was updated successfully, but these errors were encountered:
🚀 Feature
Classification metrics become task specific since 0.10, meaning use shall import
<Task><Metric>
or set a task inMetric(task=<task>)
which resolved much confusion of automatic task estimation. Also, the0.10
set this task as optional, so it still supports leaving the decision to TM. In 0.11, we have set this task argument as required, which would break many naive users' use cases and prevent them from upgrading to the latestMotivation
Just thinking as we made this breaking change in 0.11 with the making task required, and the next will be 1.0, so to re-release all from the 0.11 series with post (so, for example,
0.11.2.post1
)so all will be rereleased
0.11.0.post1
0.11.1.post1
0.11.2.post1
0.11.3.post1
0.11.4.post1
Pitch
When we allow not passing task and hold this friction for
1.0
so, it will also be easier to communicate and for a user to decide if he stays below1.0
or after...Alternatives
Additional context
The text was updated successfully, but these errors were encountered: