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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] New bugzilla proposal
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20New%20bugzilla%20proposal&In-Reply-To=%3CAANLkTimx_NNuPXw1XRzbp%3DuRFGLco6tLy8KFNmXboZmv%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="002003.html">
<LINK REL="Next" HREF="002005.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] New bugzilla proposal</H1>
<B>Romain d'Alverny</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20New%20bugzilla%20proposal&In-Reply-To=%3CAANLkTimx_NNuPXw1XRzbp%3DuRFGLco6tLy8KFNmXboZmv%40mail.gmail.com%3E"
TITLE="[Mageia-dev] New bugzilla proposal">rdalverny at gmail.com
</A><BR>
<I>Fri Jan 7 19:04:20 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="002003.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI>Next message: <A HREF="002005.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2004">[ date ]</a>
<a href="thread.html#2004">[ thread ]</a>
<a href="subject.html#2004">[ subject ]</a>
<a href="author.html#2004">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Ok, the point of this discussion is to know what we put as:
- Products
- Components
This can be updated later (as in: adding/renaming
products/components). So we should just aim at the smallest acceptable
set, so that we can open our Bugzilla instance, see what it shows,
update and open it for actual usage.
So trying to summarize above discussion, I suggest as products:
* Mageia with components:
- installation
- software
- new software request
- release (media, process)
- (for versions, cauldron first, we'll see later for the rest)
* Websites with components:
- www
- forum
- blog
- wiki
- maint-db
- (for versions, live/dev does not make much sense here; so maybe
just numbering, maybe just no version for a start; depends on the
release process)
* Infrastructure
- ? (misc?)
If that's ok (or if we can make it smaller so that it's working), we
can move forward and set this up finally (modulo the rpm field setup,
but that's not blocking for once).
Cheers,
Romain
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="002003.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI>Next message: <A HREF="002005.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#2004">[ date ]</a>
<a href="thread.html#2004">[ thread ]</a>
<a href="subject.html#2004">[ subject ]</a>
<a href="author.html#2004">[ 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>
|
