Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #219437
| From | John Hasler <jhasler@newsguy.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) |
| Date | 2020-02-25 20:30 +0100 |
| Message-ID | <zDO42-4DI-9@gated-at.bofh.it> (permalink) |
| References | <zDMOB-3Y7-3@gated-at.bofh.it> <zDMYh-41m-7@gated-at.bofh.it> |
| Organization | Dancing Horse Hill |
Roberto writes: > On strategy would be to run testing and not update too frequently. I do that with Unstable. Works fine (but I use neither Gnome nor KDE) I follow the security list and upgrade the relevant package when I see something there that matters to me. Security fixes reach Unstable as fast or faster than they reach Stable and often aren't even relevant to Unstable since it is likely to have the newest release (which is where upstream usually fixes security bugs). I also scan debian-devel to keep any eye out for problems that might be a reason *not* to upgrade. Those have been very rare in recent years. I often update packages rather than doing a full upgrade. I always do a test update or upgrade and review the proposed changes looking closely at any proposed removals. Often when Apt can't find a workable update or upgrade path Aptitude can. Might be nice if there was a Debian deriviative based on this policy. Perhaps there is. -- John Hasler jhasler@newsguy.com Elmwood, WI USA
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Sam <debian@samueldgv.com> - 2020-02-25 19:10 +0100
Re: Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Roberto C. Sánchez <roberto@debian.org> - 2020-02-25 19:20 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) John Hasler <jhasler@newsguy.com> - 2020-02-25 20:30 +0100
Re: Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) John Cunningham <djohngo@gmail.com> - 2020-02-25 19:20 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Stefan Monnier <monnier@iro.umontreal.ca> - 2020-02-26 01:10 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Keith Bainbridge <keithrbau@gmail.com> - 2020-02-26 07:10 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Reco <recoverym4n@enotuniq.net> - 2020-02-26 14:40 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Keith Bainbridge <keithrbau@gmail.com> - 2020-02-26 14:40 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Charles Curley <charlescurley@charlescurley.com> - 2020-02-26 17:50 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Keith Bainbridge <keithrbau@gmail.com> - 2020-02-26 23:20 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Keith Bainbridge <keithrbau@gmail.com> - 2020-02-27 02:10 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Charles Curley <charlescurley@charlescurley.com> - 2020-02-27 15:10 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Stefan Monnier <monnier@iro.umontreal.ca> - 2020-02-27 15:40 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Joe <joe@jretrading.com> - 2020-02-27 16:40 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Joe <joe@jretrading.com> - 2020-02-27 16:30 +0100
Re: Understanding the two-year release cycle as a desktop user (and a Debian newcomer) Didar Hossain <didar@purlo.in> - 2020-02-29 12:10 +0100
csiph-web