CEdit: Use version instead of date #329

New Issue

mxlgv · 2026-01-30T12:12:11Z

mxlgv commented

2026-01-30 12:12:11 +00:00

Use version for example 1.0 instead of date. Usually the date is updated in the PR which can be open for a very long time due to edits. Therefore, confusion may arise when merging with main.

kolibrios/programs/develop/cedit/SRC/CEdit.ob07 Line 31 in 1173ca7b26

HEADER = "CEdit (11-jan-2026)";

Use version for example `1.0` instead of date. Usually the date is updated in the PR which can be open for a very long time due to edits. Therefore, confusion may arise when merging with `main`. https://git.kolibrios.org/KolibriOS/kolibrios/src/commit/1173ca7b2669f3ed6f37231ef7512a52029bc126/programs/develop/cedit/SRC/CEdit.ob07#L31

mxlgv added the Category/Applications Influence/Text/TYPO

labels 2026-01-30 12:13:14 +00:00

Burer commented

2026-01-30 12:25:16 +00:00

Question to discuss - should we use Semantic Versioning, or leave it to program/commit author to choose style of versioning and certain numbers for certain commits?

Question to discuss - should we use [Semantic Versioning](https://semver.org/), or leave it to program/commit author to choose style of versioning and certain numbers for certain commits?

bbzy commented

2026-02-24 04:39:13 +00:00

Hello, Notepad++ and vim and most maintained software use semantic versioning. I think its best method for removing confusion and provide better solution for understanding what patch fails, what needs to be depreciated and updated, so Semantic Versioning is better solution right?
But I have a doubt about how will we decide the current version. Should it be updated and start counting from current patch as 1.0 or do we have to look at the commit history and decide a version ?

Hello, Notepad++ and vim and most maintained software use semantic versioning. I think its best method for removing confusion and provide better solution for understanding what patch fails, what needs to be depreciated and updated, so Semantic Versioning is better solution right? But I have a doubt about how will we decide the current version. Should it be updated and start counting from current patch as 1.0 or do we have to look at the commit history and decide a version ?

mxlgv commented

2026-02-24 15:31:03 +00:00

I don't think there's any point in worrying about this. I suggested 1.0 because the project is essentially finished and working. I think major.minor is sufficient.

I don't think there's any point in worrying about this. I suggested 1.0 because the project is essentially finished and working. I think `major.minor` is sufficient.

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KolibriOS/kolibrios#329