[FFmpeg-trac] #3611(trac:new): Ticket timestamps on https://trac.ffmpeg.org are in the future
FFmpeg
trac at avcodec.org
Sat Aug 29 21:45:23 CEST 2015
#3611: Ticket timestamps on https://trac.ffmpeg.org are in the future
-------------------------------------+--------------------------------
Reporter: grepfor | Owner:
Type: defect | Status: new
Priority: minor | Component: trac
Version: unspecified | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+--------------------------------
Comment (by grepfor):
I don't know, I've not attempted to reproduce it since the original
report. If you can suggest a way that I can try to reproduce it by filing
some sort of "test" tickets that don't wind up annoying people, I'll be
glad to do so and report what I find.
As for the snarky phrase "very important": Time skews between servers and
underlying databases are not necessarily without consequences: Makefiles,
database consistency checks, date/time related queries can all be affected
in subtle ways by time skews. I reported the issue because it is something
that I would have wanted to know about if I were an administrator of such
a system.
The ticket was filed with priority "normal", then reverted to "minor". Per
the definitions of ticker priority defined here
http://git.videolan.org/?p=ffmpeg.git;a=blob_plain;f=doc/issue_tracker.txt;hb=HEAD
"normal" has no definition at all, and "minor" is defined as:
"Bugs about things like spelling errors, "mp2" instead of "mp3" being
shown and such. Feature requests about things few people want or which do
not make a big difference."
In view of the above, I see no grounds for implying in a seemingly
sarcastic way that the issue was considered to be "very important". Can
you suggest a more constructive course of action upon noticing a problem,
however minor, than filing a ticket on it?
If you can't make any such constructive suggestion, then let me suggest to
you to avoid snarky comments to bug reporters who are trying, in whatever
tiny way such as this, to contribute something of value or point out a
potential problem.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/3611#comment:4>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list