From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-December/010490.html | 102 +++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010490.html (limited to 'zarb-ml/mageia-dev/2011-December/010490.html') diff --git a/zarb-ml/mageia-dev/2011-December/010490.html b/zarb-ml/mageia-dev/2011-December/010490.html new file mode 100644 index 000000000..75d96ee99 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010490.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2

+ Florian Hubold + doktor5000 at arcor.de +
+ Thu Dec 15 20:51:12 CET 2011 +

+
+ +
Am 15.12.2011 20:24, schrieb Maarten Vanraes:
+> Op donderdag 15 december 2011 19:25:22 schreef Florian Hubold:
+>> Am 15.12.2011 00:16, schrieb Maarten Vanraes:
+>>> if QA doesn't have time to do these extreeme testing, then it shouldn't
+>>> be done. and only backport.
+>>>
+>>> i guess that's my pov
+>> For backports the same QA would be mandatory. How is that a solution?
+>> Backports is not the place to drop untested updates, it's just for
+>> everything else than pure bugfix or security updates.
+> For backports QA is mandatory, but not in the same level, or it would be 
+> updates... it's imho also not doable to test this just as well as updates.
+Huh? From what i remember the only difference between backports
+and updates should be that backports are mostly new versions,
+new features, but the QA should be the same. If that's not the case,
+seems my memory from the last few meetings played tricks on me.
+
+If the only QA test for backports shall be: try if it installs and
+opens up without problems, then we should discuss this again.
+>
+>
+> backports is a new version. it means it's an upgrade project for people. it 
+> means you will backup your files and test it first, then put into production.
+Are you sure each one who would use backports would see this
+the same way as you? IMHO they'll be: Cool, a new version, must install ...
+>  
+>> Just do a full backup, try the rebuilt update, and if it's really not OK
+>> revert to the older packages and your backup. Everything else seems
+>> to foggy to me.
+> myeah, how many people do that when applying the daily updates? i wonder...
+That was specifically meant for you, not for everyday updates, also
+this is no everyday update. If you're brave enough you can also try to do without
+those safety measures, but then don't complain afterwards nobody warned you ...
+
+ + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1