Skip to content

Conversation

@renetapopova
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@NataliaIvakina NataliaIvakina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just two comments as it was done in the U&M guide

Given a version number `MAJOR.MINOR.PATCH`, the increment is based on:
2025.01.0 introduces a new calendar versioning (CalVer) for the Neo4j server instead of semantic versioning (SemVer), which was previously used.
The new versioning format, *YYYY.MM.Patch*, is based on the year and month of the release, for example, 2025.01.0, 2025.02.0, and so on.
The patch number is incremented for each release within the same month and reset to 0 at the beginning of each month.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It may be a stupid question, but why at the beginning of each month? Usually we release at the end of month. I don't think there is any connection between patch number and time of month.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! I guess it was the case at some point in time. 😄

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I took this from the document about versioning.

renetapopova and others added 2 commits January 9, 2025 14:49
Co-authored-by: NataliaIvakina <82437520+NataliaIvakina@users.noreply.github.com>
Co-authored-by: NataliaIvakina <82437520+NataliaIvakina@users.noreply.github.com>
@neo-technology-commit-status-publisher
Copy link
Collaborator

neo-technology-commit-status-publisher commented Jan 9, 2025

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

@renetapopova renetapopova merged commit 1d43ab9 into neo4j:dev Jan 9, 2025
8 checks passed
@renetapopova renetapopova deleted the dev-new-versioning branch January 9, 2025 15:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants