| Message ID | 20161208083615.00003e11@mi.rr.com |
|---|---|
| State | Rejected, archived |
| Headers | show |
2016-12-08 14:36 GMT+01:00 compn <tempn@mi.rr.com>:
> yeah.
Instead I would suggest to clarify / correct the entry or write a new one.
Carl Eugen
Hi, On Thu, Dec 8, 2016 at 8:42 AM, Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote: > 2016-12-08 14:36 GMT+01:00 compn <tempn@mi.rr.com>: > > yeah. > > Instead I would suggest to clarify / correct the entry or write a new one. I agree with CE here, let's not rewrite history. My reading of the vote is that we, as a project, are now promising to update, maintain and improve ffserver and that if this succeeds (see Nicolas' original post for official definition of this), ffserver can stay. Ronald
2016-12-08 16:02 GMT+01:00 Ronald S. Bultje <rsbultje@gmail.com>: > Hi, > > On Thu, Dec 8, 2016 at 8:42 AM, Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote: > >> 2016-12-08 14:36 GMT+01:00 compn <tempn@mi.rr.com>: >> > yeah. >> >> Instead I would suggest to clarify / correct the entry or write a new one. > > > I agree with CE here, let's not rewrite history. > > My reading of the vote is that we, as a project, are now promising to > update, maintain and improve ffserver No. We will try to do so. Carl Eugen
L'octidi 18 frimaire, an CCXXV, Ronald S. Bultje a écrit : > My reading of the vote is that we, as a project, are now promising to > update, maintain and improve ffserver and that if this succeeds (see > Nicolas' original post for official definition of this), ffserver can stay. Your reading is wrong. The result of the vote is: STOP WASTING YOUR TIME THINKING ABOUT FFSERVER since you do not care about it, it is SOMEBODY ELSE'S PROBLEM, NOT YOURS. Regards,
On Thu, Dec 08, 2016 at 10:02:13AM -0500, Ronald S. Bultje wrote: > Hi, > > On Thu, Dec 8, 2016 at 8:42 AM, Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote: > > > 2016-12-08 14:36 GMT+01:00 compn <tempn@mi.rr.com>: > > > yeah. > > > > Instead I would suggest to clarify / correct the entry or write a new one. > > > I agree with CE here, let's not rewrite history. +1 [...]
Hi, On Thu, Dec 8, 2016 at 10:04 AM, Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote: > 2016-12-08 16:02 GMT+01:00 Ronald S. Bultje <rsbultje@gmail.com>: > > Hi, > > > > On Thu, Dec 8, 2016 at 8:42 AM, Carl Eugen Hoyos <ceffmpeg@gmail.com> > wrote: > > > >> 2016-12-08 14:36 GMT+01:00 compn <tempn@mi.rr.com>: > >> > yeah. > >> > >> Instead I would suggest to clarify / correct the entry or write a new > one. > > > > > > I agree with CE here, let's not rewrite history. > > > > My reading of the vote is that we, as a project, are now promising to > > update, maintain and improve ffserver > > No. > > We will try to do so. Uh, right, that's probably better, yes. Ronald
On Thu, 8 Dec 2016 16:07:02 +0100 Nicolas George <george@nsup.org> wrote: > L'octidi 18 frimaire, an CCXXV, Ronald S. Bultje a écrit : > > My reading of the vote is that we, as a project, are now promising to > > update, maintain and improve ffserver and that if this succeeds (see > > Nicolas' original post for official definition of this), ffserver can stay. > > Your reading is wrong. > > The result of the vote is: > > STOP WASTING YOUR TIME THINKING ABOUT FFSERVER > since you do not care about it, it is > SOMEBODY ELSE'S PROBLEM, NOT YOURS. > > Regards, > Duh, then we can just remove the deprecated APIs and not care about ffserver breaking? OK, fine. But I bet you would reject a commit disabling ffserver default build.
On Thu, 8 Dec 2016 08:36:15 -0500 compn <tempn@mi.rr.com> wrote: > yeah. > > -compn -1
diff --git a/src/index b/src/index index c203676..f6c925f 100644 --- a/src/index +++ b/src/index @@ -86,15 +86,6 @@ <p> We recommend users, distributors, and system integrators, to upgrade unless they use current git master. </p> - <h3 id="ffserv">July 10th, 2016, ffserver program being dropped</h3> - <p> - After thorough deliberation, we're announcing that we're about to drop the ffserver program from the project starting with the next release. - ffserver has been a problematic program to maintain due to its use of internal APIs, which complicated the recent cleanups to the libavformat - library, and block further cleanups and improvements which are desired by API users and will be easier to maintain. Furthermore the program has - been hard for users to deploy and run due to reliability issues, lack of knowledgable people to help and confusing configuration file syntax. - Current users and members of the community are invited to write a replacement program to fill the same niche that ffserver did using the new APIs - and to contact us so we may point users to test and contribute to its development. - </p> <h3 id="pr3.1.1">July 1st, 2016, FFmpeg 3.1.1 "Laplace"</h3> <p> <a href="download.html#release_3.1">FFmpeg 3.1.1</a>, a new point release from the 3.1 release branch, is now available!