Your graph and statistics on this is great, thank you! Timo Röhling <roehl...@debian.org> writes:
> 2. Source packages going through NEW merely because they introduce new > binary packages are typically processed faster than completely new > ones. Good point. Therefore, I think your graph gives a biased view for anyone who thinks of NEW processing time to be the same as processing time to add a new source package to the archive. Is it possible from your data sources to filter these two cases apart? That is, to get a graph showing the processing time in NEW for adding a new source package. Maybe I've just been unlucky with my new source package uploads, but a 48 hours median doesn't match my experience uploading new source packages for the last 6 months. I would guess a median of say 10 days for my uploads (with exceptions down to hours and 3+ months), which is impressingly quick interrupt-based volunteer time (thank you!) but enough different from your conclusion that I suspect there is some bias. > The difficulty to know how long the trip through NEW will take has a > significant psychological impact. Close to my home, there is a railway > crossing on a relatively busy track. If the barriers come down, it can > mean a wait time from a minute (a single train) up to 20(!) minutes > (with several and/or long trains in close sucession). This does not > happen very often, but you have no way of knowing in advance. Thus, > people take significant detours to avoid that level crossing, as > they'd rather add five minutes for certain to their trip than roll the > dice for an unlucky quarter hour. Yay, thanks for this analogy! It helps to explain that not everything is captured by simple statistics. /Simon
signature.asc
Description: PGP signature
