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/2011-December/010266.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/2011-December/010266.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010266.html | 162 |
1 files changed, 162 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010266.html b/zarb-ml/mageia-dev/2011-December/010266.html new file mode 100644 index 000000000..0a54a7c8c --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010266.html @@ -0,0 +1,162 @@ +<!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=%3C4EDFFD8C.2020209%40mageia.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010261.html"> + <LINK REL="Next" HREF="010271.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] MariaDB 5.5.18 on cauldron tonight</H1> + <B>Thomas Backlund</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=%3C4EDFFD8C.2020209%40mageia.org%3E" + TITLE="[Mageia-dev] MariaDB 5.5.18 on cauldron tonight">tmb at mageia.org + </A><BR> + <I>Thu Dec 8 00:58:04 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010261.html">[Mageia-dev] MariaDB 5.5.18 on cauldron tonight +</A></li> + <LI>Next message: <A HREF="010271.html">[Mageia-dev] MariaDB 5.5.18 on cauldron tonight +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10266">[ date ]</a> + <a href="thread.html#10266">[ thread ]</a> + <a href="subject.html#10266">[ subject ]</a> + <a href="author.html#10266">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Maarten Vanraes skrev 7.12.2011 22:31: +><i> Op woensdag 07 december 2011 20:38:16 schreef Thomas Backlund: +</I>>><i> After Alpha2 I guess we need to discuss this on a council meeting to +</I>>><i> get a decision for Mageia 2. +</I>><i> +</I>><i> fine, i don't see the need of why to have a council meeting wrt this though... +</I>><i> +</I> +Sorry for being unclear, I was just pointing out that if we cant agree +on the ml, council has the power to decide. + +><i> lemme know when there _IS_ a good moment to submit +</I>><i> +</I> +Fact is... I'm very much interested in mariadb, and given Oracles track +record, I suspect soon mariadb will be the only real choice. +And since I know who upstream is, I have no problem switching... + + +The thing I reacted against is the bad timing and even worse test planning. + +You suggested to push mariadb in the middle of a big kde upgrade, wich +pretty much means half part would have been built against mysql and the +rest against mariadb... (yes I know it should work tecnically, but...) +And then you suggested that if it does not seem to work we pull it back +out 2 days later -> meaning no real time to test, and messing it up +even more... thats not how you do proper testing/qa... + + +There must be a _way_ better longterm plan to get people to really +think about it... + + +So here is what I suggest: + + +After Alpha2 ISOs are relased to the mirrors: +1. announce the upcoming push on -dev ml to remind people +2. push mariadb to core/release obsoleting/replacing _all_ of + mysql. +3. rebuild _everything_ that normlly builds against mysql to make + sure it builds correctly against mariadb and still works after + + +Now for thq QA / testing part: +1. we use mariadb in Alpha3 (planned 2012 Jan. 12) and keep + fixing any bugs that might show up. +2. around ~10 days before Beta1 (planned 2012 Feb. 21) we evalute + the situation... if it still seems to work, keep using mariadb + for Beta1 +3. final call: 1-3 days before version freeze (planned 2012 Mar. 7) + This it the point of no return... Here we decide if we go mariadb + or mysql for Mageia 2. Whatever we decide at this point is not up + for discussion anymore after this, as version freeze will be + enforced (with small reservation for KDE/Gnome release schedules) + This way we have Beta2 (planned 2012 Mar. 15) and RC (planned + 2012 Apr. 10) to flush out any problems we might get by reverting + to mysql. + + +And to be more specific about all needed testing for mariadb: +- testing all apps built against mariadb +- testing by creating all kinds of databases in mysql, and see + if mariadb is capable of upgrading/supporting them +- testing if sql clients still work when accessing (remote) + mysql servers. +- for those that feel brave, try to put it into live setups + + +How does this plan sound ? + +-- +Thomas +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010261.html">[Mageia-dev] MariaDB 5.5.18 on cauldron tonight +</A></li> + <LI>Next message: <A HREF="010271.html">[Mageia-dev] MariaDB 5.5.18 on cauldron tonight +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10266">[ date ]</a> + <a href="thread.html#10266">[ thread ]</a> + <a href="subject.html#10266">[ subject ]</a> + <a href="author.html#10266">[ 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> |