3 ms·
LTS – I don't have time to fool around upgrading and taking my system down. Maybe I can budget time for this yearly, but only if it takes a couple hours max. B
by trebor 10y ago
LTS – I don't have time to fool around upgrading and taking my system down. Maybe I can budget time for this yearly, but only if it takes a couple hours max.
Background updates – don't prompt me unless it's a breaking change; do it over night, lunch, any time I'm not actually using the app/library.
1-click backup – give me a brain-dead simple way to configure automatic backups to an external HD, Amazon S3/Glacier, etc; provide built-in support for MySQL/MariaDB backups, and similar sensitive applications.
Actually keep up with patches! For instance, I set up PHP/Apache and PHP is still on patch-level 15 — when p43 is available. Actually keep up. I don't have the time necessary to build my PHP versions from source just to keep them patched.
Sane defaults. Fast boot. Make it work out of the box with few choices, and simple to add on development environments.
Just some scattered thoughts for y'all. (Thanks for asking.)
- mattdm 10y agoLTS: See my comment below on upgrades. It should be minutes, not hours, and although Fedora does update every six months, we overlap intentionally and skip-a-release upgrades are supported. So this, I think, you should have now. Background updates: needs work. It's a good suggestion. Backup: ditto. Patches: I'm not quite sure what you mean. We do attempt (and I believe usually accomplish) patching security updates and severe bugs quickly. Sometimes, we backport security fixes rather than advancing the version number. Sane defaults: That's hard to argue with. :) Do you have anything specific in mind? Thanks for the feedback.
- mattdm 10y agoUpdate: I just upgraded my main workstation, which is heavily customized and has a lot of random stuff installed. Took 26 minutes and 40 seconds from the time I started until I was back in Firefox and able to tweet about it. About 5 minutes of that was downloading and I could keep working, so there was really only about 20 minutes of downtime.