debianwashere wrote:What would a more informed opinon be?
Official statement : As mentioned above, packages in stable-proposed-updates aren't yet officially part of Debian Stable and one should not assume is has the same quality and stability (yet!). Those new versions of the packages needs to be reviewed (by the stable release manager) and tested (by some users) before entering stable. Unofficial statement : However, the quality is usually very high (It should still be considered higher quality than Debian Testing, Backports... ) You are welcome to test those updates if you can recover minor problems (but don't test on production servers .
It should be noted that packages from security.debian.org are copied into the p-u-new (o-p-u-new) directory automatically. At the same time, packages that are uploaded directly to proposed-updates (oldstable-proposed-updates) are not monitored by the Debian security team.
Not very.debianwashere wrote:Since we're on the topic of proposed-updates: how different is the software in proposed-updates from stable?
Ideally none.How many more features does it have?
As little as possible.In longer terms: insofar as it's possible to generalize, how significant are usually the changes to packages in proposed-updates?
As required.And how commonly are they made?
No.Testing packages (almost) never go into stable.
As the version of a package gets continually updated the same "version flow" should I imagine run through proposed-updates and testing. So any version in proposed-updates would once have been in testing. Is this correct?
Compatibility with the rest of stable - and for 'oopses'.So how much is there really left to test in proposed-updates?
AdrianTM wrote:There's no hacker in my grandma...
Users browsing this forum: No registered users and 4 guests