Hacker News Reader

zypper takes care of most of that for us - it really is an exceptional package manager

We have some tests in openQA that keep an eye on upgrades, as well as some users who like to stagger their Tumbleweed updates for some weeks.

I think the record I heard was like 3 months (and our gcc5 migration happened during those months), and then they upgraded with no problem

View on HN

3 months? That's peanuts. Having too many Arch boxes, back in '12/'13 I had one that was 9 months behind, with the big filesystem movearound and sysvinit->systemd change happening in that period. It took a couple of hours of work, but the upgrade went through fine in the end.

I'd suggest you do automated testing of at least 6 month old system upgrades. Because users are going to do it, and much complaining will ensue when it breaks their system.

We do automated testing from our 'traditional' distributions, including versions that existed BEFORE Tumbleweed in it's current form..like 13.1, 12.3, etc..

So in that case, we're going back years ;)

Reply on news.ycombinator.com