Closed
Bug 1389046
Opened 8 years ago
Closed 8 years ago
Add information FIREFOX_DEVEDITION about devedition in Product Details
Categories
(www.mozilla.org :: Product Details, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rhubscher, Assigned: Sylvestre)
References
Details
Attachments
(1 file)
Today https://product-details.mozilla.org/1.0/firefox_versions.json
Contains the following:
> {
> "FIREFOX_NIGHTLY": "57.0a1",
> "FIREFOX_AURORA": "54.0a2",
> "FIREFOX_ESR": "52.3.0esr",
> "FIREFOX_ESR_NEXT": "",
> "LATEST_FIREFOX_DEVEL_VERSION": "56.0b1",
> "LATEST_FIREFOX_OLDER_VERSION": "3.6.28",
> "LATEST_FIREFOX_RELEASED_DEVEL_VERSION": "56.0b1",
> "LATEST_FIREFOX_VERSION": "55.0"
> }
It give the last version of Firefox releases:
Nightly : FIREFOX_NIGHTLY
Aurora : FIREFOX_AURORA
Beta : LATEST_FIREFOX_DEVEL_VERSION
Release : LATEST_FIREFOX_VERSION
ESR : FIREFOX_ESR
But it doesn't contains the Firefox Dev Edition.
Yesterday, Dev Edition is 55.0b14 while Beta was released as 55.0rc1
Today Dev Edition matches Beta version number.
Comment 1•8 years ago
|
||
My understanding was that Beta and Dev Edition would always match now that Aurora is gone. Sylvestre could hopefully clear this up for us though (added NI for him).
Flags: needinfo?(sledru)
Assignee | ||
Comment 2•8 years ago
|
||
We can have cases where we didn't push devedition or we didn't push beta.
Like, if we have a blocking bug on devedition, we would still push beta only until we fixed the devedition bug.
Flags: needinfo?(sledru)
Comment 3•8 years ago
|
||
We can't currently handle that on the site then since all of the info we have is about beta. So it's possible that we could have broken links to dev edition if beta ships but deved doesn't. Should we add a key specific to dev edition to product-details?
Reporter | ||
Comment 4•8 years ago
|
||
> Should we add a key specific to dev edition to product-details?
Yes that what I would expect.
Assignee | ||
Comment 5•8 years ago
|
||
I will take care of it on the ship-it & product details sides
Assignee: nobody → sledru
Assignee | ||
Updated•8 years ago
|
Blocks: dawn-project
Assignee | ||
Comment 6•8 years ago
|
||
Assignee | ||
Updated•8 years ago
|
Summary: Add information about devedition in Product Details → Add information FIREFOX_DEVEDITION about devedition in Product Details
Assignee | ||
Comment 7•8 years ago
|
||
Done:
$ curl -s https://product-details.mozilla.org/1.0/firefox_versions.json|grep FIREFOX_DEVEDITION
"FIREFOX_DEVEDITION": "56.0b6",
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Comment 8•8 years ago
|
||
Just an FYI: I'm updating our scripts to work with the new "FIREFOX_DEVEDITION" key (thanks Sylvestre!), but it seems that the "FIREFOX_AURORA" value is now empty. This is causing our update scripts to see the data as invalid. I'm fixing them now, but this does mean that product-details will not update on www.mozilla.org until it's fixed. I hope to get it fixed in prod by tomorrow at the latest. Just depends how long code review and testing takes.
Assignee | ||
Comment 9•8 years ago
|
||
ok, sorry about the empty aurora :(
I think we can wait until tomorrow.
Comment 10•8 years ago
|
||
Great. I may have it done today, but I'm glad it's not a rush so we don't have to revert anything. I'm working on the bedrock PR now. I've already fixed our data-updater[0].
Thanks again!
[0] https://ci.us-west.moz.works/blue/organizations/jenkins/product-details-json-watch/activity/
Comment 11•8 years ago
|
||
Everything is fixed and updates are working.
You need to log in
before you can comment on or make changes to this bug.
Description
•