On 06. 12. 22, 9:38, Dominique Leuenberger / DimStar wrote:
As much as another group of people DOES care to stay relevant in a Factory-First model for SLE/ALP. It's not news that Tumbleweed is the distro running ahead of SLE/ALP in helping ensuring to find issues before the changes reach the commercial products (with a lot of openQA in order to not abuse the TW-userbase as guinea pigs).
How much worth do you see for a commercial entity to sponsor workforce on something that has little to no benefit to them in the end? If they still have to do all the work a 2nd time for the commercial products, because whatever is being tested/used outside is not representative?
Sorry, but this is not the case. Even if TW didn't follow Factory-first rule here, the test base of all the things is quite large. So the above is not true at all. So if any manager has a problem with this, let me talk to them. Following your "little benefit" argument above, the compiler will be most of the time different in TW and any other/older distro (be it ALP or Leap). So the nuances between compilers (and compiler flags) will be much more different than v0 vs v2 would be now. That is, would they have to do the work 2nd time only because TW will be at gcc 13 and Leap at gcc 12? No. regards, -- js suse labs