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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Proposal of a backporting process
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C201106281447.31194.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="006072.html">
<LINK REL="Next" HREF="005977.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proposal of a backporting process</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C201106281447.31194.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] Proposal of a backporting process">stormi at laposte.net
</A><BR>
<I>Tue Jun 28 14:47:31 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006072.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI>Next message: <A HREF="005977.html">[Mageia-dev] Backports policy proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6091">[ date ]</a>
<a href="thread.html#6091">[ thread ]</a>
<a href="subject.html#6091">[ subject ]</a>
<a href="author.html#6091">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
Le vendredi 24 juin 2011 02:09:55, Michael Scherer a écrit :
><i> - a packager decide to do it. Based on the policy ( outlined in another
</I>><i> mail ), and maybe seeing with the maintainer first about that for non
</I>><i> trivial applications, the backport can be done, or not. The criterias
</I>><i> for being backported or not are not important to the process, just
</I>><i> assume that they exist for now ( and look at next mail ). So based on
</I>><i> criteria, someone say "it can be backported, so I do it".
</I>><i>
</I>><i> - I am not sure on this part, but basically, we have 2 choices :
</I>><i> - the packager take the cauldron package and push to backport testing
</I>><i> - the packager move the cauldron package in svn to backport, and there
</I>><i> send it to backport testing.
</I>><i>
</I>><i> Proposal 1 mean less work duplication, but proposal 2 let us do more
</I>><i> customization.
</I>><i>
</I>
If we want to be able to set stricted requires between backports to allow safe
cherry-picking, is it OK to do it in cauldron without any side effects ? Or
should we change the spec file only in the backport branch of the package
(which then would mean option 2) ?
Best regards
Samuel Verschelde
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006072.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI>Next message: <A HREF="005977.html">[Mageia-dev] Backports policy proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6091">[ date ]</a>
<a href="thread.html#6091">[ thread ]</a>
<a href="subject.html#6091">[ subject ]</a>
<a href="author.html#6091">[ 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>
|
