3 ms·

It is a rolling release, that means each time a new version of a package is available they will try and incorporate it. Apparently the difference they have to g

It is a rolling release, that means each time a new version of a package is available they will try and incorporate it. Apparently the difference they have to gentoo, arch et al is that they have a large CI that actually inspects screen shots to verify that the new package didn't break anything. I run antergos (arch based) at home, having the bleeding edge is nice, but the AUR is really what seals the deal for me. That being said I have been cut by the bleeding edge at least twice, once so badly that it booted up without the eth0 interface. Maybe tumbleweed wouldn't have this problem as often.

rbrownsuse 11y ago
It's probably worth mentioning that the openSUSE Build Service pretty much fills the same role as AUR http://software.opensuse.org http://software.opensuse.org lets you search across all the available repositories and easily install packages on your Tumbleweed installation Sure, those repositories are not tested, unlike the main Tumbleweed distribution, but then again, AUR isn't exactly expected to be a wholly reliable resource, just a useful one :)
toyg 11y ago
CI tests as described are very good for minor patches, but new features and significant UI changes seem to require significant manual updates to tests anyway.
- rbrownsuse 11y ago
  You'd be surprised how little a problem it is in the real world In the case of UI changes, openQA can have it's 'needles' updated in it's webUI. Look at the new screenshot, compare to the old screenshot, tell openQA to like the new stuff, done. In the case of functionality or workflow changes, yeah, tests need to be adapted, but the openQA test writing language is pretty human friendly, describing the steps that humans actually do, so it's not that hard to alter And because we test at the point of submission before anything is merged to the distribution, we generally catch the behaviour changes as part of the package submission, then we have developers keen to get their stuff in the distribution happy to help tune up the tests ;)

rbrownsuse 11y ago

It's probably worth mentioning that the openSUSE Build Service pretty much fills the same role as AUR http://software.opensuse.org http://software.opensuse.org lets you search across all the available repositories and easily install packages on your Tumbleweed installation Sure, those repositories are not tested, unlike the main Tumbleweed distribution, but then again, AUR isn't exactly expected to be a wholly reliable resource, just a useful one :)

toyg 11y ago

CI tests as described are very good for minor patches, but new features and significant UI changes seem to require significant manual updates to tests anyway.

rbrownsuse 11y ago
You'd be surprised how little a problem it is in the real world In the case of UI changes, openQA can have it's 'needles' updated in it's webUI. Look at the new screenshot, compare to the old screenshot, tell openQA to like the new stuff, done. In the case of functionality or workflow changes, yeah, tests need to be adapted, but the openQA test writing language is pretty human friendly, describing the steps that humans actually do, so it's not that hard to alter And because we test at the point of submission before anything is merged to the distribution, we generally catch the behaviour changes as part of the package submission, then we have developers keen to get their stuff in the distribution happy to help tune up the tests ;)