2008/3/25, Carlos López <[EMAIL PROTECTED]>: > > Hi Tobias and everyone else, > > ---------------------------------------- > > Date: Tue, 25 Mar 2008 06:57:06 +1300 > > > From: [EMAIL PROTECTED] > > To: yoper-dev@lists.yoper.com > > > Subject: Re: [yoper-dev] 3.1 Release Planning > > > > > Hi Carlos, > > > > Sounds good to me. > > > > Regarding delays. In order to accept a delay the bug would need to be > > grave , a recession and we'd also see how to solve that issue. There's > > no point in delaying the release if we are not able to resolve an > > issue within a certain time frame. So gotta be careful here. > > > Yes, I also agree there is no reason to delay the final release just for a > few minor uncompleted issues. However, what I meant to say it's that, > acconding with the proposed release plan, the time gap between alpha and > beta will be 15 days and the same applies from beta to final. In my opinion, > the step from beta to final release should be a bit more throughly tested, > that's why I would extend it another 15 days what would give us a whole > month just for testing purposes. During this time we should ask for massive > community testing so every bug can be sorted out before the release deadline > arrives. By extending the beta-to-final release gap not also will improve the > final output, but also will give confidence to the whole community. Can you > imagine any major distro (Fedora, Ubuntu, Debian, ...etc) having only 15 days > from beta to final release? Sorry folks, but I can't...! >
How about a compromise here ? If we get the feedback and the feedback is persistent ( allowing us to work with testing people on improvements ) then it makes sense to delay as you actually will have an improvement. From the last releases the feedback was not always of the quality allowing us to work with it. So question here is, how do we improve the quality of the testing crowd ? > > > And you're absolutely right regarding user communication. I wanted to > > mention that as well , but did not find the right words. We definitely > > need to get users involved again. And there needs to be clear > > communication. I hope someone ( new ) will step up supporting us in > > that respect. I just can't see myself blogging and hyping about Yoper, > > despite the fact it's absolutely awesome :) . > > > > I think we should purposely target the bit more adventurous and > > courageous linux user that still likes to have his working desktop , > > but is able to handle the odd glitch. Because for that crowd Yoper is > > the perfect match. A real new linux user needs a bigger community that > > has every answer ready for him /her , ( that we may have not ) . I > > think that's something we can also express in our schemes and desktop > > layout. What do you guys think ? I really would not mind to have a > > bit more technical desktop theme in 3.1 . > > > > regards > > > I hope someone jumps on board soon. There are many things any of the current > team can't manage: new website, a more eye-candy and tidy desktop, easier > hardware configuration, the well-known YIS (Yoper InStaller), boot splash, > functional resume and hibernation capabilities and many other intereting > things. Anyway, I think it's time to give someting new to the Yoper > community, everything else will come in due time... > > Regards! :) > > > > > -- > > Tobias Gerschner > > Yoper Linux - www.yoper.com > > > > Knowing is not enough; we must apply. Willing is not enough; we must do. > > > _______________________________________________ > > yoper-dev mailing list > > yoper-dev@lists.yoper.com > > http://lists.frank-hosting.de/cgi-bin/mailman/listinfo/yoper-dev > > _________________________________________________________________ > > MSN Noticias > http://noticias.msn.es/comunidad.aspx -- Tobias Gerschner Yoper Linux - www.yoper.com Knowing is not enough; we must apply. Willing is not enough; we must do. _______________________________________________ yoper-dev mailing list yoper-dev@lists.yoper.com http://lists.frank-hosting.de/cgi-bin/mailman/listinfo/yoper-dev
