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
Thanks for the comments! I'm not sure about 1, I would do every change to main with an automatic date update. Something like 2024.03.10 (and 2024.03.10.1, 2024.03.10.2, ... if needed). Regarding 2, IIRC, only stable models are required to have PyPI-installable dependencies, right?
Here is a list of things that need to happen before we can release on PyPI:
have a discussion with everyone for the release cadence & version numbers
I actually like the idea of YEAR.major.minor. The big MD packages are now doing this as well. I like the fact that users see directly how old their used version is. Other opinions?
The text was updated successfully, but these errors were encountered:
During the meeting, we decided to go toward YEAR.patch as a version number, i.e. the first release in 2024 would be 2024.0, the next one 2024.1, then 2024.2, and so on.
We should decide on the version scheme that we should use. I collected some former comments:
@frostedoyster:
@Luthaf
I actually like the idea of YEAR.major.minor. The big MD packages are now doing this as well. I like the fact that users see directly how old their used version is. Other opinions?
The text was updated successfully, but these errors were encountered: