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

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

+ Gustavo Giampaoli + giampaoli.gustavo at gmail.com +
+ Tue Oct 5 16:01:57 CEST 2010 +

+
+ +
Maybe here could fit "my" idea of "core" repo.
+https://www.mageia.org/pipermail/mageia-discuss/20101001/001761.html
+
+In fact, what you need to define is what's the "core" system.
+
+Then you could see "core system" will be updated every X month.
+Example: you decide to update core system every 12 month.
+
+So, "core system 2011" will last 12 month. But during those 12 month
+you provide constantly updates / upgrades for all the rest of the
+software that isn't part to "core".
+
+And of course, for "core system 2011" updates / bug fix / security
+patches / etc.
+
+During those 12 month, you can work in "core system 2012".
+
+Here, the "rolling" part is the "non-core" software that is constantly updated.
+
+This way "core system" becomes more stable every day during the whole
+year. But without getting older because in every moment you have the
+latest GIMP or Thunderbird available.
+
+Cheers!
+
+
+
+Gustavo Giampaoli (aka tavillo1980)
+
+ + + + + + + + +
+

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