Tor Browser Alpha version not displayed correctly

The current version of Tor Browser Alpha displays as: -beta (14.0a2) rather than 128.1.0-beta (14.0a2). This string also is pre-populated in the Google Play Store when uploading a new release.

@pierov suggested this is a tor-browser-build issue: tor-browser#42658 (comment 3063568)

assigned to @pierov

added 14.0 stable Android Bug Next labels

For comparison, stable's current string is 115.2.1-release (13.5.2).

If possible it would be nice to swap this around so future releases are something like 14.0.1 (128.0.1esr) or 14.5a1 (128.0.6esr) or something.

mentioned in issue tor-browser#42658 (closed)

marked this issue as related to tor-browser#42753 (closed)

assigned to @clairehurst

Copy and pasta problem by me.

[% c('var/fenix_version') %] should be [% c('vartorbrowser_version/') %]

If possible it would be nice to swap this around so future releases are something like 14.0.1 (128.0.1esr) or 14.5a1 (128.0.6esr) or something.

We can remove -$variant for this.

@clairehurst do you want to do it or do you prefer me to steal this one?

assigned to @pierov and unassigned @clairehurst

moved from tor-browser#43077 (moved)

marked this issue as related to #41215 (closed)

The comment is interesting:

# We put the tor-browser version last to avoid int-parsing errors when consumers of project.versionName
# assume it starts with a major version number, as it does for all Mozilla version names.

Maybe we can put a 0. prefix (e.g., 0.tbb-nightly.2024.07.30) if we see that the nightly builds fail, or use var/browser_series as a prefix, or put var/geckoview_version instead of var/fenix_version and keep it similar to the previous one.

I will try to build one soon.

We should try to fit this in 14.0a1, so that we can check whether Google Play sees this like a version downgrade.

(But I guess nothing of this will be a problem, since the previous alpha started with -, and Google Play accepted it).

mentioned in merge request !1024 (merged)

closed

removed Next label