On Mon, 6 Feb 2017 14:57:18 -0600 Don Armstrong wrote: [...] > On Mon, 06 Feb 2017, Francesco Poli wrote: > > I mean: too many data gets similar to the absence of data. > > It often says "NO release-critical bugs were closed and NONE were > > opened." and many previous changes have already vanished from the > > page. > > Ah; that's a legitimate feature request. It should probably keep track > of bugs which had been opened/closed in the previous 24H (or perhaps > longer) time period.
Thanks for converting my considerations into a feature request. I think 24 hours is fine, with a clear distinction among the various updates. Something like: Recent changes Mon Feb 6 20:00:00 UTC 2017 3 release-critical bugs were closed and 2 were opened. Closed: pkg1: #xxxxxx, #yyyyyy pkg2: #zzzzzz Opened: pkg3: #aaaaaa, #bbbbbb Mon Feb 6 19:00:00 UTC 2017 NO release-critical bugs were closed and NONE were opened. Mon Feb 6 18:00:00 UTC 2017 1 release-critical bugs were closed and NONE were opened. Closed: pkg4: #cccccc Mon Feb 6 17:00:00 UTC 2017 [...] and so forth... Or maybe even better: Recent changes 3 release-critical bugs were closed and 2 were opened. Closed: pkg1: #xxxxxx, #yyyyyy pkg2: #zzzzzz Opened: pkg3: #aaaaaa, #bbbbbb Previous changes Mon Feb 6 19:00:00 UTC 2017 Mon Feb 6 18:00:00 UTC 2017 Mon Feb 6 17:00:00 UTC 2017 [...] where each date is a link to a dedicated page where the corresponding changes are listed (only the latest 23 such pages are retained). I hope this feature may be implemented soon. Thank you very much for your time and patience! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpTsOJUD8EH5.pgp
Description: PGP signature
