Closed Bug 1315020 Opened 8 years ago Closed 7 years ago

Releases should be sorted by version, not by submittedAt

Categories

(Release Engineering :: Applications: Shipit, defect)

Product:
Release Engineering
Component:
Applications: Shipit
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

Details

We have recently shipped 47.0.2 while 49.0.2 was the latest release. 

https://github.com/mozilla-releng/ship-it/blob/master/kickoff/model.py#L285 uses

qry.order_by(table._submittedAt.desc()).limit(40)

to fetch the releases.

If we marked the 47.0.2 release as shipped it would appear as latest and would affect jsonexport and product-detail. As a result we could have 47.0.2 as latest version on the main download web site instead of 49.0.2
Bug 1321400 should address this.
Assignee: nobody → rail
in production
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: Applications: ShipIt (backend) → Applications: ShipIt
You need to log in before you can comment on or make changes to this bug.