From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20110110/002050.html | 100 ++++++++++++++++++++++++++++++++ 1 file changed, 100 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110110/002050.html (limited to 'zarb-ml/mageia-dev/20110110/002050.html') diff --git a/zarb-ml/mageia-dev/20110110/002050.html b/zarb-ml/mageia-dev/20110110/002050.html new file mode 100644 index 000000000..e431742e0 --- /dev/null +++ b/zarb-ml/mageia-dev/20110110/002050.html @@ -0,0 +1,100 @@ + + + + [Mageia-dev] New bugzilla proposal + + + + + + + + + +

[Mageia-dev] New bugzilla proposal

+ Romain d'Alverny + rdalverny at gmail.com +
+ Mon Jan 10 09:35:13 CET 2011 +

+
+ +
On Mon, Jan 10, 2011 at 00:46, Michael Scherer <misc at zarb.org> wrote:
+> Le vendredi 07 janvier 2011 à 19:04 +0100, Romain d'Alverny a écrit :
+>> So trying to summarize above discussion, I suggest as products:
+>> [...]
+>>  * Websites with components:
+>> [...]
+>>    - (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)
+>
+> If we intend ( and Buchan do, and I am sure that Stormi also ) to reuse
+> and let people reuse some of the web software we wrote outside of Mageia
+> ( ie, Buchan spoke of having identity to be proposed to the openldap
+> community ), I would keep website for the installation we have, and also
+> treat them as software for people who deployed it on their own server.
+> But that doesn't apply to everything, obviously.
+>
+> So in website, we treat our instances, and then I think that depend on
+> the number of instance we have. Even if I doubt we will have more than
+> "stable" "no stable" ( or trunk / stable, whatever the name ).
+
+Yep. Ok, so for Mageia web apps/sites, we start with a single
+"production" version and leave the possibility to have the software
+code available in the Software products or in any other upstream
+bugtracker.
+
+>>  * Infrastructure
+>>    - ? (misc?)
+>
+> I do think that people should fill bug report against me elsehwere than
+> on mageia bugzilla.
+
+:D
+
+> For infrastructure, I guess we can simply put 1 product, and later
+> decide once we see what is buggy ( because we did not plan to have bugs
+> yet, so we cannot tell where they should be filled ).
+
+Sounds good yes.
+
+> Maybe say that we review the component every year with bug triage team ?
+
+Or whenever raised as necessary, yes.
+
+Romain
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1