diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010271.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010271.html | 135 |
1 files changed, 135 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010271.html b/zarb-ml/mageia-dev/2011-December/010271.html new file mode 100644 index 000000000..9bdd12993 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010271.html @@ -0,0 +1,135 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] MariaDB 5.5.18 on cauldron tonight + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20MariaDB%205.5.18%20on%20cauldron%20tonight&In-Reply-To=%3C201112080135.08015.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="010266.html"> + <LINK REL="Next" HREF="010250.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] MariaDB 5.5.18 on cauldron tonight</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20MariaDB%205.5.18%20on%20cauldron%20tonight&In-Reply-To=%3C201112080135.08015.alien%40rmail.be%3E" + TITLE="[Mageia-dev] MariaDB 5.5.18 on cauldron tonight">alien at rmail.be + </A><BR> + <I>Thu Dec 8 01:35:07 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010266.html">[Mageia-dev] MariaDB 5.5.18 on cauldron tonight +</A></li> + <LI>Next message: <A HREF="010250.html">[Mageia-dev] No meeting tonight +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10271">[ date ]</a> + <a href="thread.html#10271">[ thread ]</a> + <a href="subject.html#10271">[ subject ]</a> + <a href="author.html#10271">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op donderdag 08 december 2011 00:58:04 schreef Thomas Backlund: +[...] +><i> Sorry for being unclear, I was just pointing out that if we cant agree +</I>><i> on the ml, council has the power to decide. +</I> +ah, ok + +[...] +><i> You suggested to push mariadb in the middle of a big kde upgrade, wich +</I>><i> pretty much means half part would have been built against mysql and the +</I>><i> rest against mariadb... (yes I know it should work tecnically, but...) +</I>><i> And then you suggested that if it does not seem to work we pull it back +</I>><i> out 2 days later -> meaning no real time to test, and messing it up +</I>><i> even more... thats not how you do proper testing/qa... +</I> +i understand your pov; tbh, after reading mikala's mail, i had misunderstood +that 4.7.4 was already completely pushed, and so that it was not in the middle +of the big KDE upgrade, but after it. (i've only realized my misinterpretation +after speaking with mikala about it) + +[...] +><i> How does this plan sound ? +</I> +It sounds good, something like this i had in mind, i hadn't shown the real +plan yet, as i just wanted a bit more testing. I only mentioned the worst case +scenario there ... (thanks for taking your time on this proposal, it's nicely +detailed (i guess i still should take some communication lessons)) + +but yeah, your plan sounds good, i'll try to make sure everything is in order +by then. + +as a reminder, i'm mentioning that 5.5 branch is _not_ released yet, but has +all the fixes already from 5.2 to 5.3 to 5.5 (mysql versioning is a bit odd, in +the way that the 5.3 and 5.5 are mostly the same; though after 5.5 versioning +should be clearer), however upstream said that the planning should allow to be +released as final before februari. + +at this bzr point, all the code is ready, all the fixes are in; now they are +allotting time to fix all the new tests (mostly adapting tests) and build +errors in non-standard builds; and also some user-specified patches, such as +the ones i submitted from the ones we're still carrying over from mysql. + +Yesterday, there is discussion going on, on how to do versioning for +libclient, since by default gcc exports all; which we have workarounds for. +I've presented our workaround, so that they could take also our distribution +into account for this matter, so by any chance we'll be able to really clean +up our build/patches (hopefully). + +AL13N +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010266.html">[Mageia-dev] MariaDB 5.5.18 on cauldron tonight +</A></li> + <LI>Next message: <A HREF="010250.html">[Mageia-dev] No meeting tonight +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10271">[ date ]</a> + <a href="thread.html#10271">[ thread ]</a> + <a href="subject.html#10271">[ subject ]</a> + <a href="author.html#10271">[ 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> |