diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-December/020479.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-December/020479.html | 186 |
1 files changed, 186 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-December/020479.html b/zarb-ml/mageia-dev/2012-December/020479.html new file mode 100644 index 000000000..6bbd3f5e5 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-December/020479.html @@ -0,0 +1,186 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Mageia 1 EOL. + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mageia%201%20EOL.&In-Reply-To=%3C50BB2E49.5000109%40apostrophe.co.uk%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="020480.html"> + <LINK REL="Next" HREF="020482.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mageia 1 EOL.</H1> + <B>Robert Wood</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mageia%201%20EOL.&In-Reply-To=%3C50BB2E49.5000109%40apostrophe.co.uk%3E" + TITLE="[Mageia-dev] Mageia 1 EOL.">robert.wood at apostrophe.co.uk + </A><BR> + <I>Sun Dec 2 11:32:41 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="020480.html">[Mageia-dev] Mageia 1 EOL. +</A></li> + <LI>Next message: <A HREF="020482.html">[Mageia-dev] Mageia 1 EOL. +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20479">[ date ]</a> + <a href="thread.html#20479">[ thread ]</a> + <a href="subject.html#20479">[ subject ]</a> + <a href="author.html#20479">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>FWIW, I agree wholeheartedly with having a longer support time. Getting +Mageia 1 right on my laptop was a long and painful process; I feel I've +only just got it going (OK, it's a year down the line really) and I have +to go through it all again in a few weeks. I accept it might be much +easier because the kernel improves at light speed, but it would much +rather not have to do it for a while! + +I run Mageia 2 on my desktop and the one and [from my perspective] the +only thing that is better about it is GIMP 2.8. I miss nothing +whatsoever other than that. Even if it was two years rather than +eighteen months it would be great. + +Just my tuppence worth. I am very, very grateful for the fantastic work +everyone does on this distribution whatever happens. :~) + +On 02/12/12 06:46, blind Pete wrote: +><i> David Walser wrote: +</I>><i> +</I>>><i> Pierre Jarillon wrote: +</I>>>><i> Le dimanche 2 décembre 2012 01:11:44, Thomas Backlund a écrit : +</I>>>>><i> Mageia 1 is now EOL. +</I>>>>><i> +</I>>>>><i> BS is locked down and updates_testing wiped. +</I>>>>><i> +</I>>>>><i> Blog post pushed and mail sent to updates-announce ML. +</I>>>><i> I have several systems installed with Mageia 1 and I wish to move them to +</I>>>><i> Mageia 3 (I make always a new install). During 4 or 5 month, I agree to +</I>>>><i> have no improvements or no bug corrections but security updates are +</I>>>><i> useful. +</I>>>><i> +</I>>>><i> I dont' want to replace Mga1 with Mga2 and 4 month later play again for +</I>>>><i> Mga2 to Mga3. I have also other machines with Mga2 and with Mandriva +</I>>>><i> 2010.2. I dont need a LTS but a Short Term Support is a bad thing and I +</I>>>><i> don't want to waste my time. +</I>>>><i> +</I>>>><i> Is it possible to have security updates until a month after Mga3 is out? +</I>>><i> My feeling on this is that we have an 18 month support cycle *because* we +</I>>><i> have a 9 month development cycle, so we support for the length of two +</I>>><i> release cycles, so that if one release causes major problems, or you don't +</I>>><i> have time to upgrade every single time, you can skip one +</I>>><i> release and still stay supported. This works fine unless a release gets +</I>>><i> delayed like Mageia 2 did (which is fine) and probably most will a +</I>>><i> little bit at least. I believe the support should continue to run until +</I>>><i> release+2 is out. +</I>><i> Sounds like a good reason for having a support period of either one +</I>><i> and a half or two and a half release cycles. Aiming for exactly +</I>><i> an integer means that there will be a day where updating has to happen. +</I>><i> Worse when there is a delay the overlap could be negative. +</I>><i> +</I>>><i> The problem is there isn't a company with paid employees providing the +</I>>><i> support, it's a community distro with all volunteers, so we can only +</I>>><i> continue to provide support if there are people willing and able to do the +</I>>><i> work. +</I>><i> One and a half release cycles? +</I>><i> +</I>><i> Perhaps future realeases could have; +</I>><i> 9 month release cycle, +</I>><i> 12 month "full" support, +</I>><i> 15 months "partial" support? +</I>><i> +</I>>><i> As you may know, I do a lot of the packaging work on security updates. I +</I>>><i> also depend on some other packagers to do some of that work, but as time +</I>>><i> passes, less and less of them have either the time or willingness to +</I>>><i> continue to work on Mageia 1, so it gets more difficult to continue +</I>>><i> to support everything as time passes. Also, even if we can get updates +</I>>><i> packaged, we need QA people to test them, and we continue to need +</I>>><i> more help with QA, as it's a very small number of people doing the vast +</I>>><i> majority of the work. QA is responsible for not only testing updates for +</I>>><i> stable distros, but also testing every single ISO (including alphas, +</I>>><i> betas, and RCs) we release. +</I>>><i> +</I>>><i> So, to make a long story short, extending support for Mageia 1 was +</I>>><i> discussed by the council, but unfortunately rejected, mostly IINM because +</I>>><i> of the burden on QA. Again, that's not to blame anyone, but QA is a lot +</I>>><i> of work that's done by few people. So if they're not willing or able to +</I>>><i> continue to support it, unless new people step up to fill that void, we +</I>>><i> just don't have the ability to continue to provide support. +</I>>><i> +</I>>><i> As the person who does a lot of the packaging for security updates, I am +</I>>><i> willing to continue the work I do on it, especially since I haven't had +</I>>><i> time yet to move my and my family's workstations to Mageia 2, and probably +</I>>><i> won't until late December, but I don't have a way to +</I>>><i> distribute any new packages. The build system has closed for Mageia 1. +</I>>><i> SVN should still be open, so I suppose I could check things in there +</I>>><i> and anyone interested could build from it locally? I don't want to host +</I>>><i> my own repository somewhere. +</I> +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="020480.html">[Mageia-dev] Mageia 1 EOL. +</A></li> + <LI>Next message: <A HREF="020482.html">[Mageia-dev] Mageia 1 EOL. +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#20479">[ date ]</a> + <a href="thread.html#20479">[ thread ]</a> + <a href="subject.html#20479">[ subject ]</a> + <a href="author.html#20479">[ 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> |