Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.project > #14005

Re: Debian - Release Cadence Options

From Russ Allbery <rra@debian.org>
Newsgroups linux.debian.project
Subject Re: Debian - Release Cadence Options
Date 2025-10-18 12:40 +0200
Message-ID <LHcvU-65ZJ-5@gated-at.bofh.it> (permalink)
References <LGyI9-5Fqi-3@gated-at.bofh.it> <LGT0d-5SPL-33@gated-at.bofh.it> <LGUyZ-5TWK-17@gated-at.bofh.it> <LGVY5-5UIL-1@gated-at.bofh.it> <LH1h7-5Ygu-5@gated-at.bofh.it>
Organization The Eyrie

Show all headers | View raw


Antoine Le Gonidec <vv221@debian.org> writes:

> In my 15 years of user support, a huge majority of reported problems
> were with testing. But the sample might be biased by testing being the
> one chosen by less experienced users, wrongly thinking it would be some
> kind of middle ground between stable and unstable.

I think so, but of course I don't really know.

All I want to be sure the original poster realizes is that if you use
unstable, your system *will* break sometimes in ways that you will have to
manually fix. I have a pretty light footprint on a system and things tend
to weirdly break less for me than for other people, and I still have to
semi-manually unbreak something at least a couple of times a year. (I also
run a testing system and have basically never had a problem with it, but
this is just one possibly unrepresentative data point.)

If you know how to do the things that I mentioned, unstable can be a great
experience. I've used unstable on some of my systems for something like 20
years now. But I'm pretty unphased by having to manually clean up
something or file a bug report and downgrade a package.

-- 
Russ Allbery (rra@debian.org)              <https://www.eyrie.org/~eagle/>

Back to linux.debian.project | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

RE: Debian - Release Cadence Options Greg McPherran <gm@mcpherranweb.com> - 2025-10-16 18:10 +0200
  Re: Debian - Release Cadence Options Mechtilde Stehmann <mechtilde@debian.org> - 2025-10-16 18:40 +0200
  Re: Debian - Release Cadence Options Colin Watson <cjwatson@debian.org> - 2025-10-17 14:40 +0200
  Re: Debian - Release Cadence Options "Jonathan Dowland" <jmtd@debian.org> - 2025-10-17 15:50 +0200
  RE: Debian - Release Cadence Options thomas@goirand.fr - 2025-10-17 15:50 +0200
    RE: Debian - Release Cadence Options Greg McPherran <gm@mcpherranweb.com> - 2025-10-17 17:30 +0200
      Re: Debian - Release Cadence Options Russ Allbery <rra@debian.org> - 2025-10-17 19:00 +0200
        Re: Debian - Release Cadence Options Antoine Le Gonidec <vv221@debian.org> - 2025-10-18 00:40 +0200
          Re: Debian - Release Cadence Options <tomas@tuxteam.de> - 2025-10-18 07:00 +0200
            Re: Debian - Release Cadence Options Antoine Le Gonidec <vv221@debian.org> - 2025-10-18 16:10 +0200
              Re: Debian - Release Cadence Options tomas@tuxteam.de - 2025-10-18 17:00 +0200
              Re: Debian - Release Cadence Options Mathias Behrle <m9s@mailbox.org> - 2025-10-19 02:30 +0200
            Re: Debian - Release Cadence Options Andrey Rakhmatullin <wrar@debian.org> - 2025-10-18 17:00 +0200
              Re: Debian - Release Cadence Options <tomas@tuxteam.de> - 2025-10-18 18:40 +0200
          Re: Debian - Release Cadence Options Russ Allbery <rra@debian.org> - 2025-10-18 12:40 +0200
          Re: Debian - Release Cadence Options "Martin Dosch" <martin@mdosch.de> - 2025-10-18 16:10 +0200
      Re: Debian - Release Cadence Options Marc Haber <mh+debian-project@zugschlus.de> - 2025-10-18 12:40 +0200
      Re: Debian - Release Cadence Options Greg McPherran <gm@mcpherranweb.com> - 2025-10-18 16:10 +0200

csiph-web