On 04/17/2015 at 09:55 AM, Lisi Reisz wrote: > On Friday 17 April 2015 14:43:53 The Wanderer wrote: > >> I do generally wait a week or three after a new stable release >> before dist-upgrading, and I _always_ review the apt-listchanges >> report for any dist-upgrade before giving the go-ahead to proceed >> with it, but that's about the limit of how far I go to avoid >> new-testing chaos. > > But you _do_ wait a little! I didn't suggest long. ;-)
I generally wait at least a week (give or take a day or three) between dist-upgrades even when testing isn't new, so this isn't as much of a change as it might seem. My point is that it's easy to take this approach even with sources.list naming testing explicitly, simply by not initiating the actual upgrade. There's no need to track a release by codename, even temporarily, in order to avoid the chaos. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
