Hi,
In that case what does it take to become a maintainer for this package?
Are there any docs on how the build process works?
Regards,Patrick
On Wed, 20 Jan 2021 18:00:45 +0100 Salvatore Bonaccorso <
car...@debian.org> wrote:> Hi,> > On Mon, Jan 11, 2021 at 05:23:50PM
+0100, Michel Le Bihan wrote:> [...]> > The window for getting in
Bullseye will close soon and this issue is> > blocking. Will you be
able to maintain Chromium in Bullseye? I can help> > with it if
needed.> > Thanks for you both which were involved in the last two
rounds of> updates for chromium.> > To make it supportable in bullseye
the problem is still that due to> the hight flux of issues which appear
in chromium, one person (with> uploading permissions) commiting either
as part of the team or> commiting to regularly sponsor uploads, would
not be enought. As said> there is a high and frequent flux of issues
appering, that means if we> only have one such person, and the person
temporarily have to step> from chromium maintenance we run in the same
situation as we right now> had for buster.> > For redundancy there
should be at least a second person available up> for doing so. The task
is quite time consuming and so cannot fall back> at some point due to
need to the security team members.> > it can be for instance Mike
Gilbert (as member of the team) and Mattia> (not part of it, but
commiting to sponsoring) to make this sort of> commitment.> >
Continuing including chromium in bullseye might be the most desirable>
option indeed, but running in the situation where in the stable>
release is sitting a old version, would be worse than not having it>
and users for instance just installing it from flathub.> > Hope this
clarifies enough the security team perspective.> > Regards,> Salvatore
