On Mon, Jan 10, 2011 at 00:46, Michael Scherer m...@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
Le vendredi 07 janvier 2011 à 19:04 +0100, Romain d'Alverny a écrit :
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
On Fri, Jan 7, 2011 at 06:19, andre999 and...@laposte.net wrote:
As for documentation and translations, a while back I suggested a similar
separation, but on reflection I think it would be more useful to have flags :
1) problem with documentation (and not function)
These bugs would be best
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
On Fri, Jan 7, 2011 at 19:04, Romain d'Alverny rdalve...@gmail.com wrote:
* Mageia with components:
- installation
- software
+ RPM package
- new software request
replace with new RPM package request
- release (media, process)
- (for versions, cauldron first, we'll see later
After reading the various mails i think we coulddo like this
Product : Mageia
Componments:
- Documentation
- Installation
- RPM packages
- New Packages requests
- Release Media
- Security
- Translations
Version:
Cauldron
( and we will add the versions when they will be supported )
On Thu, Jan 6, 2011 at 5:39 PM, Michael Scherer m...@zarb.org wrote:
Le jeudi 06 janvier 2011 à 17:05 +0100, Dexter Morgan a écrit :
After reading the various mails i think we coulddo like this
Product : Mageia
Componments:
- Documentation
- Installation
- RPM packages
- New
Le jeudi 06 janvier 2011 à 17:56 +0100, Wolfgang Bornath a écrit :
2011/1/6 Michael Scherer m...@zarb.org:
For translation, shouldn't it be attached to either a software, a
website, a document than be separate ?
This is more a philosophical question. If translation bugs are filed
in a
Le jeudi 06 janvier 2011 à 17:52 +0100, Dexter Morgan a écrit :
On Thu, Jan 6, 2011 at 5:39 PM, Michael Scherer m...@zarb.org wrote:
Le jeudi 06 janvier 2011 à 17:05 +0100, Dexter Morgan a écrit :
After reading the various mails i think we coulddo like this
Product : Mageia
2011/1/6 Michael Scherer m...@zarb.org:
And for the rest, well, the bug be it in documentation, translation, or
code must follow the same lifecycle, and imho, should be grouper
logically and we should not duplicate information everywhere, with
information being version of the
On 6 January 2011 18:39, Michael Scherer m...@zarb.org wrote:
Le jeudi 06 janvier 2011 à 17:05 +0100, Dexter Morgan a écrit :
After reading the various mails i think we coulddo like this
Product : Mageia
Componments:
- Documentation
- Installation
- RPM packages
- New Packages
11 matches
Mail list logo