diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-June/016434.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016434.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016434.html | 167 |
1 files changed, 167 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016434.html b/zarb-ml/mageia-dev/2012-June/016434.html new file mode 100644 index 000000000..d7e452d38 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016434.html @@ -0,0 +1,167 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20QA%20process%20for%20GNOME%203.4.2%20for%20Mageia%202&In-Reply-To=%3C4FD72A6F.1040400%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016433.html"> + <LINK REL="Next" HREF="016551.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2</H1> + <B>Claire Robinson</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20QA%20process%20for%20GNOME%203.4.2%20for%20Mageia%202&In-Reply-To=%3C4FD72A6F.1040400%40gmail.com%3E" + TITLE="[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2">eeeemail at gmail.com + </A><BR> + <I>Tue Jun 12 13:39:27 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016433.html">[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2 +</A></li> + <LI>Next message: <A HREF="016551.html">[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16434">[ date ]</a> + <a href="thread.html#16434">[ thread ]</a> + <a href="subject.html#16434">[ subject ]</a> + <a href="author.html#16434">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 12/06/12 12:19, andre999 wrote: +><i> Olav Vitters a écrit : +</I>>><i> For Mageia 2, I'd like to: +</I>>><i> - get my act together and fix a bunch of bugs (a lot of wrong +</I>>><i> suggests/requires, resulting in bugs&crashers) +</I>>><i> - provide GNOME 3.4.2 as update +</I>>><i> +</I>>><i> But this concerns loads and loads of packages. +</I>>><i> +</I>>><i> How to best proceed? +</I>>><i> +</I>>><i> I saw mentioning that QA is really busy. How can I make this as simple +</I>>><i> as possible for QA (not for myself)? +</I>>><i> +</I>>><i> Should I: +</I>>><i> #1 : +</I>>><i> - first fix the various bugs +</I>>><i> - provide each bug as update +</I>>><i> then later: +</I>>><i> - one massive GNOME 3.4.2 update? +</I>>><i> +</I>>><i> #2 : +</I>>><i> - do everything in one go (combine 3.4.2 update with the bugfixes)? +</I>>><i> +</I>>><i> #3 : +</I>>><i> - try and split out all the changes as much as possible (e.g. +</I>>><i> evolution would need new evolution-data-server, so must be updated +</I>>><i> at the same time).. but ideally go for filing a bug per +</I>>><i> update/package? +</I>><i> +</I>><i> QA will probably have their answer, but it seems to me much easier for +</I>><i> QA to verify one or two packages at a time, meaning #3 as much as +</I>><i> possible, and then #1. +</I>><i> As far as how you do it for testing yourself (before presenting to QA), +</I>><i> you could use whatever approach seems easiest, but even there I would +</I>><i> think that #3 as much as possible would be easier. Anyway, that is how I +</I>><i> tend to approach things. +</I>><i> (#2 seems a potential nightmare, since you're bound to miss things.) +</I>><i> +</I> +Regarding the wrong requires/suggests these are probably best dealt with +on separate bugs. They will receive proper attention that way and any +affected by bug 2317 can hopefully be found so we don't have broken +updates. That would be more difficult in one large update. + +Other bugfixes and the big update I would say to follow KDE's example +and list what has been fixed with bug numbers, packages being updated, +srpm's. If the advisory is detailed it makes performing QA alot easier. + +That is my first thought anyway. We're organising a QA meeting later +this week, you're welcome to attend and ask the team. The time/date +hasn't been finalised yet. + +<A HREF="http://framadate.org/kg48uzoef3p9hitx">http://framadate.org/kg48uzoef3p9hitx</A> + +Claire +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016433.html">[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2 +</A></li> + <LI>Next message: <A HREF="016551.html">[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16434">[ date ]</a> + <a href="thread.html#16434">[ thread ]</a> + <a href="subject.html#16434">[ subject ]</a> + <a href="author.html#16434">[ 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> |