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
From the next version, posuto will use calendar versioning. The version will be of the form YYYY.MM.release.
While ideally posuto would have data and code well-separated, the truth is that they're entangled, and it doesn't really make sense to try to read future data with an old version. For old data, the compiled data cannot be re-used but the preprocessing script can be re-run to generate old data.
Because updates are closely linked to the calendar this seems like a more reasonable versioning scheme than the current one.
The text was updated successfully, but these errors were encountered:
From the next version, posuto will use calendar versioning. The version will be of the form
YYYY.MM.release
.While ideally posuto would have data and code well-separated, the truth is that they're entangled, and it doesn't really make sense to try to read future data with an old version. For old data, the compiled data cannot be re-used but the preprocessing script can be re-run to generate old data.
Because updates are closely linked to the calendar this seems like a more reasonable versioning scheme than the current one.
The text was updated successfully, but these errors were encountered: