blob: 0b5a7bd2bdb5a6c0a70d9af8e7da6456776f0af3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] How will be the realese cycle?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3CAANLkTikQS3rM8Q-0UOXJczL24z4cDg6Q2Db1e7ZO8wCZ%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000868.html">
<LINK REL="Next" HREF="000844.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How will be the realese cycle?</H1>
<B>Gustavo Giampaoli</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3CAANLkTikQS3rM8Q-0UOXJczL24z4cDg6Q2Db1e7ZO8wCZ%40mail.gmail.com%3E"
TITLE="[Mageia-dev] How will be the realese cycle?">giampaoli.gustavo at gmail.com
</A><BR>
<I>Tue Oct 5 16:01:57 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000868.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="000844.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#843">[ date ]</a>
<a href="thread.html#843">[ thread ]</a>
<a href="subject.html#843">[ subject ]</a>
<a href="author.html#843">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Maybe here could fit "my" idea of "core" repo.
<A HREF="https://www.mageia.org/pipermail/mageia-discuss/20101001/001761.html">https://www.mageia.org/pipermail/mageia-discuss/20101001/001761.html</A>
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)
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000868.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="000844.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#843">[ date ]</a>
<a href="thread.html#843">[ thread ]</a>
<a href="subject.html#843">[ subject ]</a>
<a href="author.html#843">[ 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>
|