3 ms·

I don't really understand how one engineer working full-time on Xorg, two weeks of QA, two months for a feature, etc. should be even remotely considered a burde

by ndiddy 3y ago

I don't really understand how one engineer working full-time on Xorg, two weeks of QA, two months for a feature, etc. should be even remotely considered a burden to a company as large as Red Hat.

jtgeibel 3y ago
Well RH is already locked into this level of maintenance support for existing RHEL releases. By dropping Xorg support now, they can fully drop this effort in a decade plus. If they keep Xorg support in new releases, it keeps pushing that horizon out further and further.
baz00 3y ago
[flagged]
- gabeaweg 3y ago
  [flagged]
- dralley 3y ago
  You missed the part where they are practically the only ones doing any X.org maintainence at all, and have been for years. Disclosure: I work for Red Hat.
  - baz00 3y ago
    Yep. I'm not saying that isn't the case. It's a zombie product. And it needs to go!
dralley 3y ago
>two weeks of QA, What he said was, a couple of weeks of QA, per stack, per hardware enablement. Given that new hardware is constantly being released every couple of months, that adds up to a lot of QA. And as they said in a followup, that's "a couple of weeks" for a team of people and not just one or two. So yeah, "two (additional) weeks of QA" wouldn't be that bad, but really it's more like "two (additional) weeks of QA, multiple times a year, for a team of multiple people". And that's not insubstantial given the meager revenue opportunities in the desktop linux market.
- ndiddy 3y ago
  Thanks for replying, that makes more sense. Since you work for Red Hat, do you happen to know what the process for certifying hardware is? I'm curious to know what goes into guaranteeing that a given hardware configuration is supported by RHEL.
  - dralley 3y ago
    I have no idea, sorry. I've never worked on any part of RHEL.
gwynforthewyn 3y ago
The author addresses this misunderstanding in a comment at https://mastodon.social/@csoriano/111490414205548053 https://mastodon.social/@csoriano/111490414205548053 The tl;dr is that the comment on one engineer's tasks and the QA that one of the chores takes weren't intended to communicate that the team was 1 person big (or, presumably, that there's only one QA chore). FWIW, my read of the wording around QA was that when a each new hardware platform is enabled, it takes 2 weeks for the whole team to work through their test cases. I assume, though I don't know, there's a lot of other QA done, such as when a new feature is added or something.

by ndiddy 3y ago

I don't really understand how one engineer working full-time on Xorg, two weeks of QA, two months for a feature, etc. should be even remotely considered a burden to a company as large as Red Hat.

jtgeibel 3y ago

Well RH is already locked into this level of maintenance support for existing RHEL releases. By dropping Xorg support now, they can fully drop this effort in a decade plus. If they keep Xorg support in new releases, it keeps pushing that horizon out further and further.

baz00 3y ago

[flagged]

gabeaweg 3y ago
[flagged]
dralley 3y ago
You missed the part where they are practically the only ones doing any X.org maintainence at all, and have been for years. Disclosure: I work for Red Hat.
- baz00 3y ago
  Yep. I'm not saying that isn't the case. It's a zombie product. And it needs to go!

dralley 3y ago

>two weeks of QA, What he said was, a couple of weeks of QA, per stack, per hardware enablement. Given that new hardware is constantly being released every couple of months, that adds up to a lot of QA. And as they said in a followup, that's "a couple of weeks" for a team of people and not just one or two. So yeah, "two (additional) weeks of QA" wouldn't be that bad, but really it's more like "two (additional) weeks of QA, multiple times a year, for a team of multiple people". And that's not insubstantial given the meager revenue opportunities in the desktop linux market.

ndiddy 3y ago
Thanks for replying, that makes more sense. Since you work for Red Hat, do you happen to know what the process for certifying hardware is? I'm curious to know what goes into guaranteeing that a given hardware configuration is supported by RHEL.
- dralley 3y ago
  I have no idea, sorry. I've never worked on any part of RHEL.

gwynforthewyn 3y ago

The author addresses this misunderstanding in a comment at https://mastodon.social/@csoriano/111490414205548053 https://mastodon.social/@csoriano/111490414205548053 The tl;dr is that the comment on one engineer's tasks and the QA that one of the chores takes weren't intended to communicate that the team was 1 person big (or, presumably, that there's only one QA chore). FWIW, my read of the wording around QA was that when a each new hardware platform is enabled, it takes 2 weeks for the whole team to work through their test cases. I assume, though I don't know, there's a lot of other QA done, such as when a new feature is added or something.