Ticket's published_versions should state series information
Bug #1530870 reported by
Łukasz Zemczak
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| CI Train [cu2d] |
Fix Released
|
Wishlist
|
Brian Murray | ||
Bug Description
Currently published_versions (in the comments) has the following structure:
published_versions = { packagename1: [ver1, ver2], packagename2: [ver3, ver4] }
This is sub-optimal and confusing during introspection as you do not know which version has been released in which series. Guessing through the version number is possible in the case of CI Train merge builds, but gets more tricky when manual uploads are taken into consideration. The proposed format:
published_versions = { packagename1: { series1: ver1, series2: ver2 }, packagename2: { series1: ver3, series2: ver3 } }
We could also record all possibly published packages for a given series by this landing (in case of re-releases), in which case the verx parts could be simply arrays.
Related branches
lp:~brian-murray/cupstream2distro/bug-1530870
- Robert Bruce Park (community): Approve
-
Diff: 37 lines (+6/-5)2 files modifiedcupstream2distro/silomanager.py (+4/-3)
tests/unit/test_silomanager.py (+2/-2)
Revision history for this message
| Robert Bruce Park (robru) wrote | #1 |
| Changed in bileto: | |
| assignee: | nobody → Robert Bruce Park (robru) |
| affects: | bileto → cupstream2distro |
| Changed in cupstream2distro: | |
| assignee: | Robert Bruce Park (robru) → Brian Murray (brian-murray) |
| Changed in cupstream2distro: | |
| status: | New → In Progress |
Revision history for this message
| Robert Bruce Park (robru) wrote | #2 |
| Changed in cupstream2distro: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
The only trick with this is that I wont' be able to retroactively change existing records. How horrible is it if I just switch this over one day? Will your script be able to handle supporting both formats?