As from time to time it can happen that bugzilla suddenly "behaves differently", I think it would be great to ease a user to correlate such a change with the deployment of updated RHBZ. Currently, the homepage lists only the most recent changes, but furthermore there is no notion of _when_ it happened. I think the solutions are (in a subjective order of preference): a. provide a link to the public ML announcement for the stated latest version (note that currently bugzilla-announce-list [1] is missing the announcement of 4.4.1013 release) - this has an advantage of providing a general direction of where to search for older changes, apparently the date of deployment is easily deduced from the date of the announcement b. state the date (preferably considering GMT/UTC zone) when the release in question was deployed - this would at least provide a hint in a before-after fashion for the questioned behavior (nobody really remembers the minor versions so as to achieve the same and the mentioned bugzilla-announce-list is unfortunately pretty separated ATM) [1] https://www.redhat.com/archives/bugzilla-announce-list/
My vote is for (b) only. The mailing list post provides no additional information than on the home page, and doesn't list internal changes (for those that have privileges to see them). The date would have to be the server date (US/Eastern) since translation into the users timezone is done at the display level, and not in the code itself) -- simon
Apologies, I managed to send the 4.4.1013 announcemenet to the internal list I'll correct that momentarily. Note that if a release does not contain any publically visible changes, there will be an announcment to the internal list but no to the public list.
Okay. So the date will be in UTC (and state that) and be the date of the earliest closed bug for that version. I choose earliest since that best represents the time that the bugs were fixed. It cannot be the last in case a bug is reopened and closed again, and an average would suffer from the same version.
This change is now live. If there are any issues, do not reopen this bug. Instead, you should create a new bug and reference this bug. -- simon