blob: e93746a3b254b2942dcf4476148ba1922dcf7539 (
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
|
<!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=%3C201106241251.31152.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="005980.html">
<LINK REL="Next" HREF="005997.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proposal of a backporting process</H1>
<B>Angelo Naselli</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C201106241251.31152.anaselli%40linux.it%3E"
TITLE="[Mageia-dev] Proposal of a backporting process">anaselli at linux.it
</A><BR>
<I>Fri Jun 24 12:51:27 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="005980.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI>Next message: <A HREF="005997.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#5988">[ date ]</a>
<a href="thread.html#5988">[ thread ]</a>
<a href="subject.html#5988">[ subject ]</a>
<a href="author.html#5988">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>><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>copy i believe. IIUC we should branch cauldron into stable relases for that
package, but what happens if the package already exists? I mean
foo 1.0.0 is in stable, a foo 1.1.0 is required and could be backported
into stable branch... we have two foo programs with their own story.
><i> WDYT ?
</I>I like the second option, but in such a way we should provide upgrades from
a stable with backports, since they follow a good feedback policy before going
to stable.
I understand QA and sysadmins are not overloaded, but there's not so much
difference between updates and backports then...
--
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/20110624/5dcdf163/attachment.asc>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="005980.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI>Next message: <A HREF="005997.html">[Mageia-dev] Proposal of a backporting process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#5988">[ date ]</a>
<a href="thread.html#5988">[ thread ]</a>
<a href="subject.html#5988">[ subject ]</a>
<a href="author.html#5988">[ 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>
|