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.
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.
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.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
