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 --- .../attachments/20120325/7c7da6a8/attachment.html | 24 ++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment.html (limited to 'zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment.html') diff --git a/zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment.html b/zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment.html new file mode 100644 index 000000000..7ac07f371 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20120325/7c7da6a8/attachment.html @@ -0,0 +1,24 @@ +

On Sun, Mar 25, 2012 at 18:11, Thierry Vignaud <thierry.vignaud@gmail.com> wrote:
+ +
On 25 March 2012 18:15, Pascal Terjan <pterjan@gmail.com> wrote:
+>> Now, in order to provide a very good Mageia 2, every package should
+>> be rebuilt with the new toolchain/glibc in order to make sure they
+>> still build _and_ work correctly (and flush out any bugs in the
+>> toolchain)
+>>
+>> Now this rebuild should be done preferably in BR order when possible,
+>> to rule out bad interaction between packages and be preferably be
+>> fully done by alpha3 or beta1 at the latest so we have time to fix
+>> it properly for Mageia 2.
+
+
(...)
+

+> Rebuilding half of the distribution now seems the best way to add bugs
+> before the release...
+
+
On the other hand, we my got bugs introduced when pushing a security
+update due to the new toolchain not having been tested with those
+packages...
+Or having packages not rebuilding when patching them for security
+fixes.
+

Yes but I think it's something that should have been done after toolchain was updated in december, or at latest around beta1/version freeze, not 2 weeks before the release candidate
-- cgit v1.2.1