blob: d7060cc91829acf885b9ab38c6aeb5444413ea65 (
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
|
<!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=%3CAANLkTi%3D0hqZV1z8Cc7%2Bg2TdoOYUJvuQ5HNUvdQwuOkVh%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="001978.html">
<LINK REL="Next" HREF="001984.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] New bugzilla proposal</H1>
<B>Wolfgang Bornath</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20New%20bugzilla%20proposal&In-Reply-To=%3CAANLkTi%3D0hqZV1z8Cc7%2Bg2TdoOYUJvuQ5HNUvdQwuOkVh%40mail.gmail.com%3E"
TITLE="[Mageia-dev] New bugzilla proposal">molch.b at googlemail.com
</A><BR>
<I>Thu Jan 6 18:43:31 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="001978.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI>Next message: <A HREF="001984.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1982">[ date ]</a>
<a href="thread.html#1982">[ thread ]</a>
<a href="subject.html#1982">[ subject ]</a>
<a href="author.html#1982">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>2011/1/6 Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>>:
><i>
</I>><i> And for the rest, well, the bug be it in documentation, translation, or
</I>><i> code must follow the same lifecycle, and imho, should be grouper
</I>><i> logically and we should not duplicate information everywhere, with
</I>><i> information being "version of the product/components".
</I>
How would you group a translation error in the documentation of rpmdrake?
How would you group a documentation error in teh documentation of rpmdrake
How would you group a translation error in rpmdrake?
><i> It is not i18n goal to triage bugs. That would be duplication in term of
</I>><i> ressources, in term of setup, etc. And so if people want to sort bugs,
</I>><i> they can join the proper team. Doing otherwise would bring complexity
</I>><i> the setup for a relatively low gain IMHO.
</I>
I did not say "i18n should triage those bugs". I said the triage team
could handle those bugs easier and send them to i18n to fix them.
But as I said, IMHO this is a question with advantages and
disadvantages on both sides.
--
wobo
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001978.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI>Next message: <A HREF="001984.html">[Mageia-dev] New bugzilla proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1982">[ date ]</a>
<a href="thread.html#1982">[ thread ]</a>
<a href="subject.html#1982">[ subject ]</a>
<a href="author.html#1982">[ 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>
|