[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Webpage to track py2removal bugs & packages



On 2019-09-03 11:56, Sandro Tosi wrote:
Within a given rdeps count it currently has secondary sorting made on
Bug No. It would polish off the forward deps if they could be used for
secondary sorting instead (highest number to lowest). Bonus points for
making the headers clickable so the reader can choose which secondary
sorting is most useful (Bug No. vs Binary Pkg vs Maintainer vs # deps)

with the latest update the table is initially sorted by (# rdeps, #
fdeps); i've also made the header clickable, so that you can sort the
table on that column, but it doesnt preserve sorting between clicks
(ie if you click columnA and then columnB, the sorting on cB will
loose entirely the sorting that previously was set on cA, so you cant
click on # fdeps and then #rdeps and expect to return to he initial
sorting).

Looks good to me. 2-state sorting is plenty good, I think.


since i've already all the information there, i was thinking if we
should start posting a status of the rdepends in each bug, would it be
worth the effort? i'm not sure i want to spam too frequently the BTS,
so what would be an acceptable frequency: once a week?  if we want to
pile on this, all the blocks/blockedby bts massaging could be done by
this script i guess?


I'm less certain about this. Once a week would be too often I think. We're at the point now where we know the python2 decommissioning needs to be done. You've given us the list of packages, we just need to go start working on them.

Drew


Reply to: