Re: [gentoo-project] Call for agenda items - council meeting 2020-03-08

[Raymond Jennings]

On Mon, Mar 2, 2020 at 3:57 AM Michał Górny <mgorny@g.o> wrote:

> On Tue, 2020-02-25 at 19:59 -0800, Georgy Yakovlev wrote:
> > Hello,
> >
> > on 2020-03-08, the Gentoo council will meet at
> > 19:00 UTC in the #gentoo-council channel on freenode.
> >
> > Please reply to this message with any items you would like us to discuss
> > or vote on.
>
> Following the discussion within the QA team, I'd like to ask the Council
> to clarify whether EAPI 4 ban applies to revision bumps as a result of
> dependency changes?
>

Personally I don't think it should, especially if the change is just fixing
something that broke.


> I think the key point in banning EAPIs is that the maintainer (or
> generally, someone caring about the package in question) should be
> responsible for the EAPI bump.  I don't think anybody should be forced
> to do that when in middle of large batch of changes (read: when I only
> touch the package because it's blocking me).
>

Seconded.


> In this particular case, I'm thinking of revbumps due to dependency
> changes.  Say, if I do a change in a dependency *I* maintain, and have
> to fix a large number of revdeps, I don't think it's fair to expect me
> to EAPI-bump some packages I don't maintain.  The main difference is
> that we're talking of dep change + revbump that can be linted via
> pkgcheck/repoman vs. EAPI bump that needs full scale testing.
>

I second the motion.

I think that certain changes can be "grandfathered" if they can be done
without breaking anything

> --
> Best regards,
> Michał Górny
>
>