Date: Fri, 12 Jul 2019 10:34:15 +0200 From: David Demelier <markand@malikania.fr> To: freebsd-ports@freebsd.org Subject: Re: ffmpeg port Message-ID: <bc258c8a-53ac-37a6-b224-e4325b767dc0@malikania.fr> In-Reply-To: <CAP7rwcjOa3xuBz66pLivnDxNifJbdR0=_xtJqyT678Y2xd6tWg@mail.gmail.com> References: <2288dfa5-0ec0-d1f5-eeca-066260604c22@aventia.pw> <1ryy-rtgr-wny@FreeBSD.org> <95f2326f-8431-804d-1439-40dbc28f71a0@malikania.fr> <CAP7rwcjOa3xuBz66pLivnDxNifJbdR0=_xtJqyT678Y2xd6tWg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 12/07/2019 à 01:17, Adam Weinberger a écrit : > We really would love to be able to provide release or LTS branches, > but it simply comes down to resources. We'd need a few people working > in paid positions to manage RE environments. The FreeBSD Foundation > (which underwrites a couple very selective paid positions) has > prioritized development of new technologies to keep FreeBSD > competitive over third-party software backporting. Hello Adam, I'm not sure how can a LTS branch that you usually never update (except CVE, security fixes) take more time than quarterly branches that you need to recreate every 3 months and do some merges. Basically, a LTS branch stay in marble for a release lifetime and will only contain sporadic commits for security fixes or vulnerabilities. That's mostly what Slackware does for a release version. For someone who wants bleeding edge, they use slackware-current. Regards, -- David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bc258c8a-53ac-37a6-b224-e4325b767dc0>