304472 - bump Firefox version on trunk to 1.6a1

Status: RESOLVED FIXED

(Firefox Build System :: General, defect)

Description

[Chase Phillips]

Bump Firefox version on trunk to 1.6a1.

Comment 1

[Thorsten 'nightrat' Fritz]

I think "1.6a1" is not allowed because of the "a" inside and the people could
get confused because of the Gecko version "1.9a1".

A possible solution would be "1.5+". But in that case all extensions would break
because of the wrong max version in their install.rdf.

Comment 2

[Benjamin Smedberg]

1.6a1 is allowed by the new version-number parser. AMO might not be updated to
allow that format yet.

Comment 3

[Chase Phillips]

Attachment: bump browser version to 1.6a1 (landed)

Comment 4

[Chase Phillips]

Comment on attachment 192789 [details] [diff] [review]
bump browser version to 1.6a1 (landed)

Checking in browser/app/module.ver;
/cvsroot/mozilla/browser/app/module.ver,v  <--	module.ver
new revision: 1.12; previous revision: 1.11
done
Checking in browser/config/version.txt;
/cvsroot/mozilla/browser/config/version.txt,v  <--  version.txt
new revision: 1.5; previous revision: 1.4
done
Checking in browser/installer/windows/installer.cfg;
/cvsroot/mozilla/browser/installer/windows/installer.cfg,v  <--  installer.cfg
new revision: 1.19; previous revision: 1.18
done

Comment 5

[Alex Ihrig [:Thunderbird_Mail_DE]]

The new version number scheme has one major problem for extension authors:

If we'd like to set extensions maxversion to something like 1.6a1, to allow
testing with the alpha/beta builds, everyone could use the extensions with the
(not yet released) 1.5 stable/final builds.

Comment 6

[Daniel C]

Comment 5: minVersion?

Comment 7

[Alex Ihrig [:Thunderbird_Mail_DE]]

(In reply to comment #6)
> Comment 5: minVersion?

No.

Setting the minVersion to 1.6a1 would break the extensions for the old 1.0.x
Thunderbird / Firefox versions.