Question

2

What is the version numbering logic for open source developers managing software releases?

rated 0 times [ 2] [ 0] / answers: 1 / hits: 367 / 2 Years ago, tue, august 16, 2022, 5:52:59

I guess this is more of a general question that I cant find the the answer to anywhere. What is the version numbering logic for open source developers managing software releases and is there any governance or guidance I can read up on. The origins of this question comes from me reviewing and researching software on countless websites that I would like to use on my Ubuntu OS.

Through experience, I am learning some sites are much better than others explaining if a release is a stable, experimental or maintenance release but these explanations are not consistent with any version numbering logic I am familiar with.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

ingsta

Add To Favorites

Follow

Total Points: 391

Total Questions: 103

Total Answers: 124

Location: Bonaire

Member since Wed, Mar 29, 2023

1 Year ago

ingsta questions

1 How to kill chromium snap from CLI?

Sun, Oct 23, 22, 01:42, 2 Years ago

1 Zoom client crashes on Ubuntu Studio 22.04 LTS

Sat, Oct 30, 21, 11:27, 3 Years ago

1 22.04 is suggested on Ubuntu's website but not in the repository

Tue, Aug 2, 22, 13:35, 2 Years ago

1 Get DKMS offline?

Sun, Nov 28, 21, 12:49, 2 Years ago

1 keyboard backlight Acer Nitro5 AN515-55 Ubuntu 20.10 works but 2 question

Sun, Jan 16, 22, 05:17, 2 Years ago

View All

answered 2 Years ago cupwire · Accepted Answer

As you probably know, there are more than one "software development methodology".

And sure, more than one "life cycle".

Some of them are "Security Driven", some "Release Driven", some "Deadline Driven", "Documentation Driven" and more...

Even if the software is open source or not, the software can be managed with any methodology, according to the goal of the project.

I think; It is better to search for the methodology of the project (if there is one, specific), and then search for it's release version control.

Example:
The project is managed with Waterfall Life Cycle Model.
That means, every step is checked, there is a big work and team is separated to certain sub-teams. (This one is not good for Open Source, because Water Fall is not for open minds)

Example 2:
The project is managed with XP, Agile:
That means, the project is story (feature) driven. Every sub-version brings new and fully-working features to latest program. And every version brings bigger changes (or may be collects goal related features together).