esr 38.3.0 nightly are not generated (or named incorrectly)

RESOLVED WORKSFORME

Status

Release Engineering
Release Automation: Other
RESOLVED WORKSFORME
3 years ago
3 years ago

People

(Reporter: sylvestre, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
In the past, we were using:
https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-esr38

Now, it should probably be:
https://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-esr38-linux/latest/

but only 31.2.1 is available while we should find 38.3.
This has come up numerous times in the past year. This is normal, and expected. Version bumps happen when the release starts - not before. This is the same thing that happens on mozilla-release.

It is less than ideal, but we don't have automation that will bump to the next version. If you would like to bump it yourself, feel free.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
(In reply to Ben Hearsum (:bhearsum) from comment #1)
> It is less than ideal, but we don't have automation that will bump to the
> next version.

IIRC, one of the reasons we don't bump the *next* version is because we don't know if there will be build2.
The goal here is to give the esr-using community a chance to test something close to what we're going to ship for ESR, a couple of weeks ahead of time. Is there a better way to do that than this, or can we bump the version now?
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #3)
> The goal here is to give the esr-using community a chance to test something
> close to what we're going to ship for ESR, a couple of weeks ahead of time.
> Is there a better way to do that than this, or can we bump the version now?

My advice would be to point them at the files, and ignore the version number. If you really want to bump the version first, make a commit like this on the default branch: http://hg.mozilla.org/releases/mozilla-esr38/rev/fa72c74dea29
You need to log in before you can comment on or make changes to this bug.