De updatemanager geeft wel aan vanaf welke versie naar welke versie je update. En ook wat de veranderingen zijn en of het een security update is.
Maar of de gemiddelde gebruiker nu iets heeft aan een lap tekst als deze, is maar de vraag:
Changes for the versions:
Installed version: 14.0.1+build1-0ubuntu2
Available version: 15.0~b1+build1-0ubuntu1
Version 15.0~b1+build1-0ubuntu1:
* New upstream release from the beta channel (FIREFOX_15_0b1_BUILD1)
[ Chris Coulson <knip e-mail> ]
* Update globalmenu-extension to 3.3
* Disable PGO again
- update debian/config/branch.mk
* Separate the package name from the application name in various places.
This enables us to change the package name without having to modify the
application or packaging (eg, to allow us to provide official branded
versions of Firefox ESR using the package name "firefox-esr")
- update debian/README.Debian.in
- update debian/apport/source_firefox.py.in
- update debian/build/get-orig-source.mk
- update debian/control{,.in}
- update debian/control.langpacks
- update debian/control.langpacks.unavail
- update debian/firefox-locale.preinst.in
- update debian/firefox.install.in
- update debian/firefox.links.in
- update debian/firefox.lintian-overrides.in
- update debian/firefox.postinst.in
- update debian/firefox.postrm.in
- update debian/firefox.preinst.in
- update debian/firefox.sh.in
- remove debian/patches/change-moz-app-name.patch
- update debian/patches/series
- update debian/rules
- update debian/usr.bin.firefox.apparmor.*
* Move parts of debian/rules that can be shared with Thunderbird to a
new, common file (mozbuild.mk)
- update debian/rules
- add debian/build/mozbuild.mk
- add debian/build/mozvars.mk
- update debian/build/testsuite.mk
* Make it possible to use the same create-tarball.py for Firefox and
Thunderbird
- update debian/build/create-tarball.py
- update debian/build/get-orig-source.mk
- add debian/config/tarball.conf
* Switch to source format 3.0
- add debian/source/format
- add debian/source/options to diff-ignore the .mozclient.mk file which
is created during clean, and to pass "--no-preparation"
- update debian/build/enable-dist-patches.pl
- rename debian/patches/series => debian/patches/series.in so the source
isn't built with patches applied
- update debian/README.source
* Goodbye embedded tarball, and our use of tarball.mk!
- update debian/build/create-tarball.py
- update debian/build/extract-file.py
- update debian/build/get-orig-source.mk
- update debian/build/mozbuild.mk
* Run the upstream cleansrcdir target during clean
- update debian/build/mozbuild.mk
* Refresh patches
- update debian/patches/mozilla-kde.patch
* Drop the plugin / abrowser / firefox-branding replaces + breaks on quantal
- update debian/rules
* Support the "parallel" option in DEB_BUILD_OPTIONS
- update debian/build/mozbuild.mk
- update debian/config/mozconfig.in
* Drop some of the complex shell script for creating language packs
- update debian/build/mozbuild.mk
- update debian/build/get-xpi-id.py
* Drop searchplugin patches - these patches are an absolute pain to maintain,
as they seem to break frequently and we have to touch each localized
plugin. Instead, just keep our own copy of plugins we modify, and add
these in to the language packs at the end of the build process
- remove debian/patches/ubuntu-codes-google.patch
- remove debian/patches/ubuntu-codes-amazon.patch
- remove debian/patches/ubuntu-codes-baidu.patch
- update debian/patches/series.in
- update debian/build/mozbuild.mk
- add debian/searchplugins/*
* Get rid of pointless python script
- remove debian/build/extract-file.py
- update debian/build/mozbuild.mk
* Add an automated check for finding search engines that match particular
patterns and verifying that they are replaced with our own search
engine if we think they should be
- add debian/build/check-search-overrides.pl
- update debian/build/mozbuild.mk
- add debian/searchplugins/overrides.json
- update debian/control{,.in}
* Drop reload-new-plugins.patch, as this shouldn't actually be needed
- remove debian/patches/reload-new-plugins.patch
- update debian/patches/series.in
* Merge get-orig-source.mk in to mozbuild.mk
- update debian/build/mozbuild.mk
- remove debian/build/get-orig-source.mk
* Handle comments in locales.blacklist
- update debian/build/refresh-supported-locales.pl
- update debian/config/locales.blacklist
* Fork the upstream text preprocessor and add support for additional
comparison operators, which means we no longer have to add new
defines for every distro version specific change we add
- add debian/build/Expression.py
- add debian/build/Preprocessor.py
- update debian/apport/source_firefox.py.in
- update debian/build/mozbuild.mk
- update debian/config/mozconfig.in
- update debian/firefox-dev.install.in
- update debian/firefox-locale.preinst.in
- update debian/firefox.desktop.in
- update debian/firefox.dirs.in
- update debian/firefox.install.in
- update debian/firefox.links.in
- update debian/firefox.postinst.in
- update debian/firefox.postrm.in
- update debian/firefox.preinst.in
- update debian/firefox.prerm.in
- update debian/rules
* Refresh shipped locales
* Drop powerpc patches, which are fixed upstream
- remove debian/patches/fix-dtoa-build-on-ppc.patch and
- remove debian/patches/fix-build-failure-without-yarr-jit.patch
- update debian/patches/series.in
* Drop fix-crashreporter-ftbfs-with-gcc4.7.patch, which is fixed upstream
[ Adam Conrad <knip> ]
* Add no_neon_on_arm.patch to skip the NEON tests on ARM, since we
don't build with NEON by default on either of our ARM architectures
Een ervaren gebruiker kan zelf bepalen of hij het wel of niet wil hebben, maar een onervaren iemand kan die beslissing niet maken lijkt me.
Overigens kan ik best begrijpen dat je voorzichtig bent met updates als het om een server gaat, of een andere computer waar je moeilijk bij kan komen (staat 100 KM verderop ofzo). Dan is het best logisch om die updates eerst te testen op een andere pc voordat je ze installeert.
Maar dan nog is het noodzakelijk om uiteindelijk de veiligheidsupdates te installeren. Zonder die updates loop je namelijk een groot risico. En ik denk dat het risico van een foute update kleiner is dan het risico dat je loopt wanneer je door blijft draaien op een gatenkaas.