From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Trac votes and priority
Date: Fri, 17 Feb 2023 23:29:04 +0100
Message-ID: <20230217222904.GC1949656@pb2> (raw)
In-Reply-To: <CAELR-fAkT+Qi_xSHzgSd_Q0+nWynaT4AeLyW862W54iY8TxXuA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1039 bytes --]
Hi
On Fri, Feb 17, 2023 at 12:25:07PM -0600, Brad Isbell wrote:
> I think that if Trac ticket priority is to be used, it should first be
> working. Currently, if you try to vote on a ticket, a `500 Internal
> Server Error` occurs in the background.
it seemed to work when i tryied but it seems trac needs some adjustments and
tuning and maintaince. It seems not configured optimally
>
> I don't think that popularity of a ticket always indicates priority or
> urgency. Security bugs are a good example... Not something most users
> know or care about but can have huge implications if not patched.
This suggestion was not supposed to mean that this would be the only
way to set priority. But an additional input. Meaning if more than X
users want something then it would be important.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
I have never wished to cater to the crowd; for what I know they do not
approve, and what they approve I do not know. -- Epicurus
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-02-17 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 22:14 Michael Niedermayer
2023-02-17 18:25 ` Brad Isbell
2023-02-17 22:29 ` Michael Niedermayer [this message]
2023-02-17 23:18 ` Michael Niedermayer
2023-02-21 9:12 ` Michael Niedermayer
2023-02-17 18:35 ` Andreas Rheinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230217222904.GC1949656@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git