blob: b1d284424f678a129f08e4e4aceb6dd652aa99a2 (
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
90
91
92
93
94
95
96
97
98
99
100
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Backports policy clarification (and discussion)
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C201206131352.51470.anaselli%40linux.it%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016450.html">
<LINK REL="Next" HREF="016275.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports policy clarification (and discussion)</H1>
<B>Angelo Naselli</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C201206131352.51470.anaselli%40linux.it%3E"
TITLE="[Mageia-dev] Backports policy clarification (and discussion)">anaselli at linux.it
</A><BR>
<I>Wed Jun 13 13:52:48 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016450.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI>Next message: <A HREF="016275.html">[Mageia-dev] Broken web link
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16454">[ date ]</a>
<a href="thread.html#16454">[ thread ]</a>
<a href="subject.html#16454">[ subject ]</a>
<a href="author.html#16454">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>mercoledì 13 giugno 2012 alle 00:53, nicolas vigier ha scritto:
><i> We are talking about backports, not updates, so we don't care about
</I>><i> versionning policy of updates. And backports can have higher version
</I>><i> than 'release' repository of next version, that's what this thread is
</I>><i> about.
</I>??? The policy should be the *same*, otherwise you won't have an upgradable
system, something is in bp for n-1 could be:
a) in core for n
b) in update for n
c) in bp for n
In any of them it should be upgradable, so why shouldn't we
follow the versioning policy for updates, since a bp for mageia n-1
*is* an upgrade/update in mageia n?
ennael could we add a point in tonight meeting? i seem we talked
a lot and reached no decisions...
Angelo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/mageia-dev/attachments/20120613/93ff3496/attachment.asc>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016450.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI>Next message: <A HREF="016275.html">[Mageia-dev] Broken web link
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16454">[ date ]</a>
<a href="thread.html#16454">[ thread ]</a>
<a href="subject.html#16454">[ subject ]</a>
<a href="author.html#16454">[ 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>
|