From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-March/013448.html | 124 ++++++++++++++++++++++++++++++ 1 file changed, 124 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-March/013448.html (limited to 'zarb-ml/mageia-dev/2012-March/013448.html') diff --git a/zarb-ml/mageia-dev/2012-March/013448.html b/zarb-ml/mageia-dev/2012-March/013448.html new file mode 100644 index 000000000..0ed26fe23 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-March/013448.html @@ -0,0 +1,124 @@ + + + + [Mageia-dev] MariaDB: problem: final estimated release date + + + + + + + + + +

[Mageia-dev] MariaDB: problem: final estimated release date

+ Colin Guthrie + mageia at colin.guthr.ie +
+ Fri Mar 23 19:34:01 CET 2012 +

+
+ +
'Twas brillig, and Maarten Vanraes at 23/03/12 17:39 did gyre and gimble:
+> ( see https://mariadb.atlassian.net/secure/Dashboard.jspa , look at road map )
+> 
+> MariaDB RC 5.5.22	29/Mar/12
+> MariaDB GA 5.5.23	09/Apr/12
+> 
+> that means that the GA (final release) is 2 days after release freeze :-(
+> (not counting any possible extra delays)
+> 
+> however, i would like to have the final release and not the release candidate.
+> 
+> any thoughts on this?
+
+Well, sh1t happens... We'll just have to go with the RC and we can
+always issue an update to the final release afterwards. I don't think
+this is a huge problem. If there happen to be delays for other reasons
+we can maybe push it in, but I wouldn't bank on it!
+
+Col
+
+
+-- 
+
+Colin Guthrie
+colin(at)mageia.org
+http://colin.guthr.ie/
+
+Day Job:
+  Tribalogic Limited http://www.tribalogic.net/
+Open Source:
+  Mageia Contributor http://www.mageia.org/
+  PulseAudio Hacker http://www.pulseaudio.org/
+  Trac Hacker http://trac.edgewall.org/
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1