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/20101002/000653.html | 74 +++++++++++++++++++++++++++++++++ 1 file changed, 74 insertions(+) create mode 100644 zarb-ml/mageia-dev/20101002/000653.html (limited to 'zarb-ml/mageia-dev/20101002/000653.html') diff --git a/zarb-ml/mageia-dev/20101002/000653.html b/zarb-ml/mageia-dev/20101002/000653.html new file mode 100644 index 000000000..df86c4872 --- /dev/null +++ b/zarb-ml/mageia-dev/20101002/000653.html @@ -0,0 +1,74 @@ + + + + [Mageia-dev] How will be the realese cycle? + + + + + + + + + +

[Mageia-dev] How will be the realese cycle?

+ David W. Hodgins + davidwhodgins at gmail.com +
+ Sat Oct 2 04:26:59 CEST 2010 +

+
+ +
On Fri, 01 Oct 2010 20:27:00 -0400, André Machado <afmachado at dcemail.com> wrote:
+
+> However, is that only one version per year - with updates of course - it would
+> be best for you?
+
+Another option, that just occurred to me. Rolling updates until
+there is an update to something like glibc, that requires the
+bulk of the rpm packages to need rebuilding.  Then, and only
+then, create a new iso/release, rather then using a set
+schedule.
+
+Regards, Dave Hodgins
+
+ + + + + + + + + +
+

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