On Sat, 2020-08-01 at 12:25 +0200, Lars Wendler wrote: > On Sat, 01 Aug 2020 12:19:13 +0200 Michał Górny wrote: > > > On Sat, 2020-08-01 at 06:15 -0400, Rich Freeman wrote: > > > On Sat, Aug 1, 2020 at 3:29 AM Michał Górny <mgo...@gentoo.org> > > > wrote: > > > > I would like to take this as an opportunity to remind you to port > > > > your packages to Python 3.7 and 3.8. According to our timeline > > > > [1], packages that are not ported by the end of the year are going > > > > to be last rited. We would also like to switch to 3.8 in December. > > > > > > > > [1] > > > > https://wiki.gentoo.org/wiki/Project:Python/Implementations#Implementation_support_timeline > > > > > > So, has anybody given thought to publishing a list of packages that > > > still need to be updated, including their maintainers? > > > > > > Or perhaps filing bugs? > > > > > > Or is the plan to go ahead and watching nothing happen for the next > > > few months, then start masking hundreds of packages, and then watch > > > devs scramble to fix problems they didn't realize existed? > > > > > > > Or perhaps you'd like to help out instead of wasting your own > > and everybody else's time on talking? > > > > Honestly... seeing such replies from you
I am sorry, I shouldn't have lost it. However, I suppose you can understand how I feel putting a lot of effort into it and hearing someone insinuate stuff like this without even checking that I've filed the bugs a few months ago. > or knowing that you do not > hesitate to hit other devs with your full QA deputy power once they > dare to touch python packages is not motivating in any way to even > consider helping you. > I would really appreciate if you didn't make such statements in public without verifying your claims first. I have never had any problems with people either joining Python team or 'touching Python packages', as long as they follow the same standards as people in Python team do. For example, this means *testing* packages. I don't see a problem with people adding py3.8 to packages. I do have a problem when people add py3.8 when there are explicit test regressions with py3.8. I might be wrong but I think it's a common sense and not something specific to Python team that you're supposed not to break stuff. Especially when you don't maintain that stuff and the resulting fallout is going to hit somebody else. Furthermore, I have no clue what 'full QA deputy power' is. I don't know what's your source, and I can only guess what person are you referring to. However, there's no such thing as 'QA deputy power', QA is making decisions as a team and I don't think there was any disciplinary action taken recently. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
