Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide on version scheme #224

Open
PicoCentauri opened this issue Jun 3, 2024 · 1 comment
Open

Decide on version scheme #224

PicoCentauri opened this issue Jun 3, 2024 · 1 comment
Labels
Discussion Issues to be discussed by the contributors Priority: Medium Important issues to address after high priority.

Comments

@PicoCentauri
Copy link
Contributor

We should decide on the version scheme that we should use. I collected some former comments:

@frostedoyster:

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?

@Luthaf

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?

@PicoCentauri PicoCentauri added Priority: Medium Important issues to address after high priority. Discussion Issues to be discussed by the contributors labels Jun 3, 2024
@Luthaf
Copy link
Member

Luthaf commented Jun 7, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Issues to be discussed by the contributors Priority: Medium Important issues to address after high priority.
Projects
None yet
Development

No branches or pull requests

2 participants