Re: [FFmpeg-devel] 5.0 blocking issues

[Michael Niedermayer <michael@niedermayer.cc>]

[-- Attachment #1.1: Type: text/plain, Size: 2536 bytes --]

On Wed, Jan 12, 2022 at 01:41:18PM -0300, James Almer wrote:
> 
> 
> On 1/12/2022 1:36 PM, Nicolas George wrote:
> > Michael Niedermayer (12022-01-12):
> > > Iam really bad at keeping track of everything everyone asks to be
> > > included and then notice when it was included fully with nothing
> > > missing and no amendmends.
> > > Maybe we could put a RELEASE_BLOCKER file in release branches in the future
> > > and everyone can list in it what needs to be done before the release
> > > and when something is done the person pushing would also remove that
> > > line from the file.
> > 
> > Maybe you could stop bothering about things you are not good at and that
> > bore you.
> > 
> > If releases need to be made, then let somebody step in for the role of
> > release manager. And if nobody steps in, let us not make releases.
> > 
> > After all, WE do not need to make releases: it is the other projects who
> > need us to make releases.
> > 
> > Regards,
> 
> I think it should be more like, as release manager, he decides when to cut a
> branch and when to tag a release within that branch, and in either case
> giving a warning with some time in advance.

Thats what i did in the past pretty much and iam more than happy with that.
but this time things didnt work that well with the branch as there was some
stuff people really wanted in. So i tried to be a bit more cautious with
"just releasing". Also the channels waiting added delay at the start.
I didnt say it previously but i think waiting for a feature like the
channels API is a bad idea. If its ready, its ready if not i think we
shouldnt connect releases to it and make it more constraint for everyone.


> Saying "Anything else?" then waiting for people and constantly postponing
> tagging is not going to work. And it's not the first time this happens.

It didnt work very well here. 


> 
> Right now the branch is made and and the feature set frozen, and anything
> that could be backported can wait until 5.0.1. Cutting the branch is when
> interested parties should spoke and be hasty as that means a feature freeze.
> But right now, the release can and should be made whenever Michael wants to.

yes, you are correct, i agree, this whole thing here unneccesarily complicated
things compared to past releases

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Asymptotically faster algorithms should always be preferred if you have
asymptotical amounts of data

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".