From: "Måns Rullgård" <email@example.com>
To: David Runge <firstname.lastname@example.org>
Subject: Re: Next release
Date: Tue, 03 Sep 2019 16:41:44 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <20190831233133.GF5960@blckbx.localdomain> (David Runge's message of "Sun, 1 Sep 2019 01:31:33 +0200")
David Runge <firstname.lastname@example.org> writes:
> Hi again,
> On 2019-05-23 18:04:18 (+0200), David Runge wrote:
>> On 2018-10-04 19:39:11 (+0200), David Runge wrote:
>> > Is there any ticket preventing a new release? If so, how can the
>> > process be helped?
>> as sox has now accumulated a total of twelve (!) CVEs for version 14.4.2
>> , I'd like to once more urge the current maintainers to tag a new
> It has been several months now since my last mail, to which I never got
> a reply and nearly a year since my first mail in regards to this topic
> (which has also been ignored).
> I find it highly concerning and by now rate it as negligent, that the
> current maintainers are seemingly eager to merge further features in,
> but not release a new version of this tool to have a stable release,
> that is not riddled with CVEs.
> I am unable to comprehend this behavior and the absolute radio silence
> in regards to this topic and once more would like to ask for a release
> of sox.
I can assure you that your demanding tone isn't going to get you a
release any sooner.
SoX-devel mailing list
prev parent reply other threads:[~2019-09-03 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 17:39 Next release David Runge
2019-05-23 16:04 ` David Runge
2019-08-31 23:31 ` David Runge
2019-09-02 11:17 ` Claude Warren
2019-09-03 15:41 ` Måns Rullgård [this message]
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).