summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/006090.html
blob: d1abe8d1b05b0ed1194ed303e1c21a9f20dbf88b (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
101
102
103
104
105
106
107
108
109
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Backports policy proposal
   </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%20proposal&In-Reply-To=%3C201106281443.35743.stormi%40laposte.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="006046.html">
   <LINK REL="Next"  HREF="005978.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Backports policy proposal</H1>
    <B>Samuel Verschelde</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20proposal&In-Reply-To=%3C201106281443.35743.stormi%40laposte.net%3E"
       TITLE="[Mageia-dev] Backports policy proposal">stormi at laposte.net
       </A><BR>
    <I>Tue Jun 28 14:43:35 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="006046.html">[Mageia-dev] Backports policy proposal
</A></li>
        <LI>Next message: <A HREF="005978.html">[Mageia-dev] Update of backport, policy proposal
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6090">[ date ]</a>
              <a href="thread.html#6090">[ thread ]</a>
              <a href="subject.html#6090">[ subject ]</a>
              <a href="author.html#6090">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>
Le vendredi 24 juin 2011 02:10:14, Michael Scherer a &#233;crit :
&gt;<i> I would also propose a few rules :
</I>&gt;<i> 
</I>&gt;<i> &quot;a package should have been in cauldron since 1 week before being
</I>&gt;<i> backported&quot;, so we can at least ensure there was a minimal test on it,
</I>&gt;<i> Ie, if I package stuff-virtual-manager, I cannot backport it before 1
</I>&gt;<i> week. If we have a package of stuff-virtual-manager since 1 month, and
</I>&gt;<i> that I update a new version, then I can backport. The idea is that a
</I>&gt;<i> newer packages may suffer from more bug than older one.
</I>
Could this apply only to &quot;-backport&quot; media and not &quot;-backport_testing &quot; media 
? I would find good to be able to send a package very quickly to 
backports_testing so that I can start to be tested as soon as possible. A 
whole week for that would be a long time, considering that after that you have 
to add more time so that the backport can be tested.

By the way I think a packager usually knows the risks there is to send a 
package too quickly to the backports and that we don't necessarily need to 
enforce such a strict &quot;1 week&quot; rule. Especially when sending to 
backports_testing first.

 
&gt;<i> - cannot be backported if this is not a leaf package, will be revised
</I>&gt;<i> later
</I>
I would like to be less strict, by replacing &quot;leaf package&quot; by &quot;leaf group of 
packages, tighly tied together by strict requires&quot;.

Examples : 
- A requires newer B and C, and no other package requires B and C (quite 
common with games where data are split into separate packages) =&gt; you can 
backport A, B, C. To me this situation should be possible.
- A requires newer B, but D depends on B too =&gt; you can't backport A and B 
alone, but if the maintainers consider it acceptable to enforce upgrade of D 
when someone wants to upgrade A or upgrade of A when someone wants to upgrade 
D (could be related pieces of software), then you can backport A, B and D (and 
make sure to set the good requires). To me this situation would be nice to 
have as an available option.

Best regards

Samuel Verschelde

</PRE>











<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="006046.html">[Mageia-dev] Backports policy proposal
</A></li>
	<LI>Next message: <A HREF="005978.html">[Mageia-dev] Update of backport, policy proposal
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6090">[ date ]</a>
              <a href="thread.html#6090">[ thread ]</a>
              <a href="subject.html#6090">[ subject ]</a>
              <a href="author.html#6090">[ 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>