Re: flavors for testing packages by testing team

[Bruno Conde <blconde@xxxxxxxx>]

Hey, so you are jozee, a great contributor to the forum, nice to exchange e-mails with you,

Very good to hear you guys are talking about the internationalization process, I don't think it would be that hard to get the things smooth, and I'm willing to contribute. So, if you think it is needed, maybe we could report an issue about it.

And if you guys think it is a good idea to split the repos into main and community, we also could open a thread in the forum to hear opinions (is there a possibility to get some threads fixed, like announcements?).

Att., 

BC



---- On Fri, 30 Apr 2010 01:04:54 -0300 Rohit Joshi <rj.rohit@xxxxxxxxx> wrote ---- 

> Hi Bruno (aka blconde), 
>  
> Reporting on forum is the fastest and the preferred way.. Everyone 
> reads it and can offer you a solution. 
>  
> After discussing on the forums, if this is a genuine problem affecting 
> a particular package/slitaz tools, please add this on lab issues. We 
> track lab issues and close the reported one as and when we have time. 
>  
> The developers are doing some private discussions about 
> internalization after your post on the forum. So, important post are 
> read and actions are taken in background :-) 
>  
> Rohit (aka jozee) 
>  
> On Thu, Apr 29, 2010 at 11:08 PM, Bruno Conde <blconde@xxxxxxxx> wrote: 
> > Hi to all, 
> > 
> > This is my first message here in the list, and I don't know for sure how it 
> > works, but here it goes my observations to Rohit's e-mail: 
> > 
> > I could test this kind of "test live cd" if someone make it, but I think the 
> > issue here is to fill the reports and whole testing environment; I didn't 
> > know it, and I'm pleased to know you folks are working on this. Sure I can 
> > help sending this kind of information. 
> > 
> > About about the repositories, here's another suggestion: what about we focus 
> > on testing a few packages besides the core packages, the popular ones just 
> > like Rohit said, and leave the other to a community repo, as Debian's 
> > Contrib or Ubuntu's Community? I believe the "popular packages list" would 
> > be something like: Abiword, Gnumeric, OpenOffice, Firefox, Pidgin, some 
> > e-mail client (I deeply prefer Thunderbird than Sylpheed/Claws), MPlayer 
> > and/or GXine, Gimp and maybe others I'm forgetting. 
> > 
> > And all these bring me to procedure question: what is the best way to 
> > quickly point out a problem, go straight report a bug to 
> > http://labs.slitaz.org/issues or first post a thread in the forum? Because I 
> > asked myself about it when I posted this: 
> > http://forum.slitaz.org/index.php/discussion/1081/translation-for-abiword-gnumeric-pidgin-and-others/ 
> > 
> > Att., 
> > 
> > BC 
> > 
> > 
> > 
> > ---- On Thu, 29 Apr 2010 21:11:50 -0300 Rohit Joshi <rj.rohit@xxxxxxxxx> 
> > wrote ---- 
> > 
> > Hi all, 
> > 
> > Claudinei and Linea are working towards creating a testing environment 
> > for better quality management (http://labs.slitaz.org/wiki/packages). 
> > Many people have shown interest in joining testing teams. But it seems 
> > very few people contributed the test reports. 
> > 
> > I think its a good effort but maybe we need to make it easier for 
> > people to test. I personally do not like people criticizing SliTaz 
> > devs over the forums that such an such thing have not been fixed for 
> > over an year. 
> > 
> > Pascal has recently announced a flavor contest 
> > (http://mirror.slitaz.org/pizza/). All official flavors 
> > (http://hg.slitaz.org/flavors/) can be automatically generated by 
> > anyone within minutes. 
> > 
> > So, maybe we simply create few 650MB testing flavors for each package 
> > category (or probably just with popular packages). I believe such 
> > large flavors can be generated based on low-ram / 3-in-1 flavor ( but 
> > haven't really tested this theory myself). 
> > 
> > I feel testing packages on liveCD is much easier. Furthermore, we can 
> > generate a new testCD with any given snapshot of cooking repos. 
> > 
> > One of the downside, however, is that this will not address all the 
> > dependency issues that may happen on SliTaz Core CD. But, atleast , 
> > this may help to catch the problems faster. Moreover, we already have 
> > implemented automatic dependency checking. 
> > 
> > I look forward to hearing your ideas and suggestions. 
> > 
> > Thanks 
> > 
> > Rohit 
> > 
> > --- 
> > SliTaz GNU/Linux Mailing list - http://www.slitaz.org/ 
> > 
> > 
> > 
>  
> --- 
> SliTaz GNU/Linux Mailing list - http://www.slitaz.org/ 
>