diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010263.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010263.html | 136 |
1 files changed, 136 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010263.html b/zarb-ml/mageia-dev/2011-December/010263.html new file mode 100644 index 000000000..62c9ce490 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010263.html @@ -0,0 +1,136 @@ +<!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=%3C201112072321.38609.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="010260.html"> + <LINK REL="Next" HREF="010264.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=%3C201112072321.38609.alien%40rmail.be%3E" + TITLE="[Mageia-dev] MariaDB 5.5.18 on cauldron tonight">alien at rmail.be + </A><BR> + <I>Wed Dec 7 23:21:38 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010260.html">[Mageia-dev] MariaDB 5.5.18 on cauldron tonight +</A></li> + <LI>Next message: <A HREF="010264.html">[Mageia-dev] MariaDB 5.5.18 on cauldron tonight +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10263">[ date ]</a> + <a href="thread.html#10263">[ thread ]</a> + <a href="subject.html#10263">[ subject ]</a> + <a href="author.html#10263">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op woensdag 07 december 2011 23:08:35 schreef Colin Guthrie: +><i> I'm perfectly willing to give it a shot (even with my earlier concerns +</I>><i> and caveats). Perhaps after alpha2 is a good idea, but I'm not against +</I>><i> doing it sooner either for wider testing (the "officialness" of an alpha +</I>><i> should mean it gets more testing... in theory!), especially as I doubt +</I>><i> it will cause any problems due to the nature of the software and it's +</I>><i> sources and who is behind it etc. If there is a problem we resubmit +</I>><i> mysql before the beta stage. +</I>><i> +</I>><i> +</I>><i> I certainly feel your frustration, (I've been in a similar situation +</I>><i> several times!), but try to be pragmatic and understand peoples' +</I>><i> concerns/paranoia (once bitten, twice shy and all that!) +</I>><i> +</I>><i> Col +</I> +i've watched part of a movie after i noticed i was stepping over the line... + +my apologies, i've cooled down now. + +I do understand the other pov, though i still maintain that the likeliness of +problems due to this is fairly low and the willingness of mariadb to get any +issues fixed fast is pretty high, the actual progress being done on mariadb is +fairly quick, there's a quite a number of developers and i got good contacts +with several developers there, who are fairly dedicated to fixing asap any +bugs. + +if there are problems i'm fairly certain we can get the help from upstream in +fixing these fast, but given what i've seen of this 5.5 branch it's unlikely to +me if there will be issues. it's sticks pretty close to mysql in order to +avoid any sort of issues that might pop up, due to this. + +i suspect for them it's more of the issue of managability and any odd +decisions from the upper management, and that's why they left mysql; the +patches that've always been denied by upper management, etc... + +from their pov, they work on mysql like they've always done, except they are +free-er to do what they want to do, if they want to accept patches from google +of facebook, they can..., if they want to add 3rd party storage engines, they +can... + +looking at it like this, it's unlikely to be much different than updating from +5.5.10 to 5.5.15 rather than updating from mysql to mariadb + +well, we'll see what happens next... + +AL13N +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010260.html">[Mageia-dev] MariaDB 5.5.18 on cauldron tonight +</A></li> + <LI>Next message: <A HREF="010264.html">[Mageia-dev] MariaDB 5.5.18 on cauldron tonight +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10263">[ date ]</a> + <a href="thread.html#10263">[ thread ]</a> + <a href="subject.html#10263">[ subject ]</a> + <a href="author.html#10263">[ 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> |