diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010504.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010504.html | 110 |
1 files changed, 110 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010504.html b/zarb-ml/mageia-dev/2011-December/010504.html new file mode 100644 index 000000000..71211a30f --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010504.html @@ -0,0 +1,110 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%09kdenlive-0.8.2-1.mga2&In-Reply-To=%3C201112152348.49970.alien%40rmail.be%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010492.html"> + <LINK REL="Next" HREF="010463.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%09kdenlive-0.8.2-1.mga2&In-Reply-To=%3C201112152348.49970.alien%40rmail.be%3E" + TITLE="[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2">alien at rmail.be + </A><BR> + <I>Thu Dec 15 23:48:49 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010492.html">[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2 +</A></li> + <LI>Next message: <A HREF="010463.html">[Mageia-dev] rsync fails at .../iso/cauldron/old +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10504">[ date ]</a> + <a href="thread.html#10504">[ thread ]</a> + <a href="subject.html#10504">[ subject ]</a> + <a href="author.html#10504">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op donderdag 15 december 2011 21:18:44 schreef Juan Luis Baptiste: +><i> On Thu, Dec 15, 2011 at 2:51 PM, Florian Hubold <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">doktor5000 at arcor.de</A>> wrote: +</I>><i> > Huh? From what i remember the only difference between backports +</I>><i> > and updates should be that backports are mostly new versions, +</I>><i> > new features, but the QA should be the same. If that's not the case, +</I>><i> > seems my memory from the last few meetings played tricks on me. +</I> +iirc in some meetings there was some discussion on QA availability with +security updates not being fixed fast enough, or something and that backports +still should contain testing, but not as much as updates, due to lack of +manpower and such. + +of course, there's been alot of meetings on backports(and less results), so i +can't really be sure of the accuracy of this last paragraph... + +><i> Well we're going off the track of the meaning of this thread but my +</I>><i> opinion on this: I agree with Marteen, it would be unrealistic on +</I>><i> thinking on putting the same amount of work of QA on backports than in +</I>><i> updates. How would be the way to go ? get a list of the new features +</I>><i> of a program and have a QA member test each one of them ?? I don't +</I>><i> think that's a good idea, it would take a lot of time and the person +</I>><i> testing should know fairly enough how the program in question works. +</I>><i> In that case the same QA should be put each time a new version of a +</I>><i> program is updated in cauldron, and that also is not possible to do. +</I>><i> +</I>><i> I think in the case of backports tests should be much more lax than in +</I>><i> updates: it installs runs and if there's any important bugfix +</I>><i> mentioned in the changelog make sure that it is fixed, there's no +</I>><i> other way around it. If not then do not have backports at all and let +</I>><i> third party repos continue to pop up to fulfill this need. +</I> +don't get me wrong, my position isn't as such that there should be less QA in +backports than in updates, but that there should be more QA in updates than +there is with backports. + +as i mentioned before, the important difference in updates and backports, is +the new features, as such backports are new versions of software, while +updates are the _same_ version and should do everything (except the bug) the +same. + +lastly, doktor5000: you say this is no everyday update... and i agree with +that. it's exactly that reason that should make this backport and not update. +(except also for our current policy on new features). + +AL13N +</PRE> + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010492.html">[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2 +</A></li> + <LI>Next message: <A HREF="010463.html">[Mageia-dev] rsync fails at .../iso/cauldron/old +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10504">[ date ]</a> + <a href="thread.html#10504">[ thread ]</a> + <a href="subject.html#10504">[ subject ]</a> + <a href="author.html#10504">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |