From: Brad Isbell <brad@audiopump.co>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Trac votes and priority
Date: Fri, 17 Feb 2023 12:25:07 -0600
Message-ID: <CAELR-fAkT+Qi_xSHzgSd_Q0+nWynaT4AeLyW862W54iY8TxXuA@mail.gmail.com> (raw)
In-Reply-To: <20230216221441.GB1949656@pb2>
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.
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.
Brad Isbell // AudioPump, Inc.
brad@audiopump.co
On Thu, Feb 16, 2023 at 4:14 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Hi
>
> Trac allows users to vote for tickets, should we bump tickets priority
> to important once they surpass some threshold of votes ?
> Should there be a difference betweem defects and enhancements ?
>
> Heres the list of tickets sorted by the number of votes
> https://trac.ffmpeg.org/report/11
>
> Thanks
>
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Avoid a single point of failure, be that a person or equipment.
> _______________________________________________
> 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".
_______________________________________________
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 18:25 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 [this message]
2023-02-17 22:29 ` Michael Niedermayer
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=CAELR-fAkT+Qi_xSHzgSd_Q0+nWynaT4AeLyW862W54iY8TxXuA@mail.gmail.com \
--to=brad@audiopump.co \
--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