On Fri, Apr 20, 2018 at 02:31:59AM +0200, Michael Niedermayer wrote: > On Thu, Apr 19, 2018 at 01:31:33PM +0200, Hendrik Leppkes wrote: > > On Wed, Apr 18, 2018 at 11:15 PM, Michael Niedermayer > > <mich...@niedermayer.cc> wrote: > > > On Wed, Apr 18, 2018 at 04:09:41PM +0200, Hendrik Leppkes wrote: > > >> On Mon, Apr 16, 2018 at 1:24 PM, Michael Niedermayer > > >> <mich...@niedermayer.cc> wrote: > > >> > On Sat, Apr 14, 2018 at 02:04:43PM +0200, Michael Niedermayer wrote: > > >> >> On Fri, Apr 13, 2018 at 12:53:08AM +0200, Michael Niedermayer wrote: > > >> >> > On Mon, Feb 19, 2018 at 02:50:08AM +0100, Michael Niedermayer wrote: > > >> >> > > Hi > > >> >> > > > > >> >> > > Its 4 months since 3.4 was branched so its time for a new major > > >> >> > > release > > >> >> > > > > >> >> > > Is 4.0 or 3.5 preferred ? > > >> >> > > Any name suggestions ? > > >> >> > > > > >> >> > > If there are no objections i will likely make that release in the > > >> >> > > next weeks > > >> >> > > > >> >> > more time has passed than intended ... > > >> >> > > > >> >> > what issues do remain that need to be fixed before the release ? > > >> >> > I see fate.ffmpeg.org is not looking that well (compared to most > > >> >> > releases in the past) i remember this being pretty much green > > >> >> > longer ago > > >> >> > do people want these to be fixed before the release ? > > >> >> > > >> >> ok, so, my plan is to create a release/4.0 branch from master in the > > >> >> next > > >> >> 24-48 hours unless theres some issue brought to my attention (CC me > > >> >> just to > > >> >> be sure if theres an issue) > > >> >> > > >> >> then wait 2 days or so and backport any newly found bugfixes to > > >> >> release/4.0 > > >> >> and then make the release finally > > >> >> > > >> >> delays at any point are possible due to issues, lack of time or other. > > >> >> > > >> >> as name i think kierans suggestion of Wu would make sense. IIRC we had > > >> >> no name suggested by more than 1 developer. Please correct me if i > > >> >> miscounted i did only briefly re-check the mails in the thread. > > >> > > > >> > > > >> > release/4.0 branched > > >> > next is the release in a few days. > > >> > If theres something i should wait for please say so and CC me > > >> > also please backport all bugfixes to 4.0 > > >> > > >> I have two more fixes that should really go in 4.0, one is the > > >> tls_schannel fix that I plan to push soon (I'm the author of that > > >> module, so unless someone says otherwise soon), and the MSVC configure > > >> breakage introduced in the last 2 days. > > >> Not sure when you planned to tag, but hopefully both of those are > > >> resolved by tomorrow afternoon. > > > > > > well i had a bad headache today and iam a bit behind now with stuff > > > so i likely wont be ready before tomorrow evening either. > > > > Both of my changes have been applied, so nothing on my side any longer. > > ok, i wanted to make the release today but its getting later than ideal. > No point in rushing this by a few hours i guess > > so next target is tomorrow early afternoon. > delays are very possible of course if anything delays it > > ill do a bit more testing before i go to sleep > > Btw if someone wants to write anything like release notes or a news > entry ...
4.0 release made, ill leave writing the news entry to people who can write english without a spell checker 4.0.1 is planned to be released in 2 weeks. Sooner if major bugs are found, later if something delays it or theres nothing major. So please continue pushing bugfixes to release/4.0 (and older release branches if you like) Thanks [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Rewriting code that is poorly written but fully understood is good. Rewriting code that one doesnt understand is a sign that one is less smart then the original author, trying to rewrite it will not make it better.
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
