Builder history should be ordered descending 'datebuilt'

Bug #234237 reported by Celso Providelo
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Michael Nelson

Bug Description

We can simply remove the ordering special case in the code which uses descending 'datebuilt' order for SUPERSEDED and ALL states and clean the old SUPERSEDED build rescords with non-empty 'builder' in production.

Revision history for this message
Celso Providelo (cprov) wrote :

in fact, when superseding a build we should clean 'builder' column.

Changed in soyuz:
assignee: nobody → cprov
milestone: none → 1.2.6
status: New → Confirmed
Celso Providelo (cprov)
Changed in soyuz:
assignee: cprov → nobody
milestone: 1.2.6 → none
Celso Providelo (cprov)
Changed in soyuz:
importance: Undecided → Medium
milestone: none → 2.1.9
status: Confirmed → Triaged
milestone: 2.1.9 → 2.1.8
Changed in soyuz:
assignee: nobody → al-maisan
milestone: 2.1.8 → 2.1.9
Changed in soyuz:
milestone: 2.1.9 → 2.1.11
Changed in soyuz:
assignee: al-maisan → michael.nelson
Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Michael Nelson (michael.nelson) wrote :

Fixed with r7288

Changed in soyuz:
status: In Progress → Fix Committed
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.