On 2017-07-21 02:37, Greg Freemyer wrote:
On Thu, Jul 20, 2017 at 8:14 PM, Carlos E. R. <> wrote:
Some times TW is released with known (and published) problems with this or that component. It is work in progress.
Is there an example of that in the last couple years?
I can't think of any. Tumbleweed is much more stable than you make it sound.
:-) Some quick examples: A major change to LDAP the other day. A very major upgrade to Perl coming. php5 drop. Python changes to version 3. gcc7. LO changing the font engine so that some fonts no longer are accepted. elevator=bfq not accepted. MonoDevelop disappears. Missing jssc in Arduino. TW thinking that a stick that was formatted as FAT is still an ISO. Leafnode not starting. Missing deps for duplicity. Base:System broken for PowerPC. NM failing after TW 20170630. /var/lock gone in some cases. ecryptfs broken.
Right now it hasn't been published in a week and one of the main reasons is it won't pass autoQA tests related to Ruby 2.2 functionality.
Back when it was called "factory" that failure would have got out to the community, but with Tumbleweed we have a large set of autoQA tests that have to pass. And when a major bug does get past autoQA, autoQA is updated to look for it the next time.
I'm not saying it's perfect, but it's pretty damn good,
Yes, it is very good. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)