1794301 - Adopting a new meaningful versioning scheme

Status: RESOLVED WONTFIX

(Firefox :: General, enhancement)

Description

[Artem S. Tashkinov]

Steps to reproduce:

Firefox is now at version 105.0.3. No one knows what it means. The second number is not even used (outside of ESR releases).

My humble proposal is to change the Firefox versioning scheme to something more meaningful.

I've always loved this scheme:

YEAR.MONTH
or
YEAR.RELEASE

For Firefox 105.0.3 that would be: 22.09.03 or 22.06.03.

Since we are already past 100 and there's no going back what about adding 100 on top of that? or even 2000?

Firefox 103.0 then will become either 122.10.0 or 122.07.0 (2022.10.0 or 2022.07.0).

What's the benefit? Being able to read the version and instantly understand whether what you're running is up to date.

Comment 1

[Robert Longson [:longsonr]]

The downside is that sites that check the version number will instantly break. Why would we want to do that to those sites?

Comment 2

[Rares Doghi, Desktop QA]

This looks like an enhancement, I do like to point out that we do show the date for our builds in Nightly 107.0a1 (2022-10-10), maybe it wouldnt be a bad idea to add the date to beta and release builds ?

Comment 3

[Artem S. Tashkinov]

(In reply to Robert Longson [:longsonr] from comment #1)

The downside is that sites that check the version number will instantly break. Why would we want to do that to those sites?

Firefox 106.0 will become Firefox e.g. 122.10.

I've no idea why would anything break in this case.

Comment 4

[Artem S. Tashkinov]

When you hit version 123 this bug becomes irrelevant :-(

Comment 5

[Wayne Mery (:wsmwk)]

ISTR this was considered some time ago but the idea was abandoned?

Comment 6

[Ryan VanderMeulen [:RyanVM]]

It's not something we're discussing.