From: Hans Verkuil <hverkuil@xs4all.nl>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
workflows@vger.kernel.org
Subject: Re: Media committers model postponed to 6.14 - Was: Re: [PATCH v3 0/3] Document the new media-committer's model
Date: Fri, 7 Feb 2025 12:54:52 +0100 [thread overview]
Message-ID: <d22d2f35-bf04-4d0c-a94c-70dcc08a945e@xs4all.nl> (raw)
In-Reply-To: <20241209091548.165e5152@foz.lan>
On 09/12/2024 09:15, Mauro Carvalho Chehab wrote:
> Em Tue, 3 Dec 2024 14:07:12 +0100
> Mauro Carvalho Chehab <mchehab+huawei@kernel.org> escreveu:
>
>>
>> The idea is to gradually open media-committers to more people, as each
>> phase succeeds, addressing infra, procedures, etc.
>>
>> My rough idea is to do:
>>
>> - Phase 0.99: beta testers;
>> - Phase 1 is to invite people that regularly submit PRs;
>> - Phase 2 is to invite other active maintainers;
>> - Phase 3 (or 2?, TBD) to open for non-maintainers.
>>
>> We shouldn't rush it, as there are a lot to be done before opening it
>> broadly. So, I would say that:
>> - phase 0.99 would start in -rc2 (if things go well during this week);
>> - phase 1 may still happen on this merge window, but as there will be
>> only a few weeks between -rc2 and -rc6, and people usually get
>> holidays in Dec/Jan, it is more likely that it will start for
>> 6.14-rc1, again if we didn't notice big issues on phase 0.99.
>>
>> We should wait at least for a couple of releases on phase 1,
>> again to cleanup process and fine-tune infra. If things go well,
>> we can move to phase 2.
>
> After some discussions with Hans, we decided to postpone the
> beta testers phase to the next kernel cycle. There are a couple of
> reasons for that:
>
> - This should give us more time to come up with a final version of
> the media-committers documentation and agreement;
Where are we with this? I haven't seen any updates since this post.
Personally, I think the CI is ready for more committers, so it would be
nice if we can get some experience with that.
Regards,
Hans
>
> - This would also work better with regards to end of year's vacations,
> as they'll be affecting at least 2/3 -rc versions. Plus, we all have
> things to finish before such vacations. So, better to start fresh next
> year;
>
> - Media CI still had issues with a patch series I submitted, as it picked
> the wrong baseline, causing CI to not test two patches that were
> applied on the top of media-committers/next branch. This was fixed
> by Ricardo, but it means that we may still need to polish CI before
> granting more people righs there.
>
> With that, if we want to start the media committers for 6.14, we should
> aim to close review this document by -rc6, or, at most, -rc7, getting
> the patches merged during the next merge window.
>
> Regard
>
> Thanks,
> Mauro
>
next prev parent reply other threads:[~2025-02-07 11:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 9:26 Mauro Carvalho Chehab
2024-12-02 9:26 ` [PATCH v3 2/3] docs: media: document media multi-committers rules and process Mauro Carvalho Chehab
2024-12-02 14:13 ` Sakari Ailus
2024-12-03 8:26 ` Mauro Carvalho Chehab
2024-12-03 10:03 ` Sakari Ailus
2024-12-02 14:37 ` Hans Verkuil
2024-12-02 15:03 ` [PATCH v3 0/3] Document the new media-committer's model Hans Verkuil
2024-12-03 7:19 ` Mauro Carvalho Chehab
2024-12-03 11:22 ` Laurent Pinchart
2024-12-03 13:07 ` Mauro Carvalho Chehab
2024-12-09 8:15 ` Media committers model postponed to 6.14 - Was: " Mauro Carvalho Chehab
2025-02-07 11:54 ` Hans Verkuil [this message]
2025-02-10 7:00 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d22d2f35-bf04-4d0c-a94c-70dcc08a945e@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=corbet@lwn.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox