Rawhide testing proposal (WAS: Re: GNOME 2.14 for FC5?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



fre, 16 09 2005 kl. 08:20 +0300, skrev Gilboa Davara:
> I disagree.
> I rather have a stable FC5 with an older KDE/GNOME then have an fairly
> stable that semi-work DE that's broken in 50 different places.
> As a couple of people (and RH devs) states in the different thread, FC4
> is/was a problematic release. Considering this, it's imperative to get a
> better, stable, FC5 out. (Even if it's not bleeding edge)
> 
> Anyways, what-ever you decide, please, please, please make sure
> gnome-pilot is working this time?
> 
> Gilboa

One of the reasons I think it's important to decide soon if FC5 will
target 2.14 or 2.12 is that if we do decide to go for 2.14, it would
make it possible to move rawhide to the 2.13.x releases as soon as
possible.

I would personally be most willing to help set up a user rawhide testing
squad, I do all my work on one box and it runs rawhide, upgraded every
day - I have a very vested interest in keeping it running on a day to
day basis, not that I personally mind a little breakage and baby eating
every once in a while, it's a calculated risk. This means filing bugs
and tracking the mailing lists for warnings.

One of the issues with GNOME .0 releases is that there simply isn't
enough testers, and the only way we'll get really stable .0 releases
would be if we actively encourage people to do so, and teach people to
file good bugs. One of the ways we can do this is to use rawhide from
early on as a testing ground for GNOME. 

I too want a high quality product from FC, that is why I brought this up
now rather than in 3 months time when release is closer and we have a
more defined image of what makes up FC5.

Having recently acquired a palm pilot I am sicked to see distributions
follow in FC4s footsteps and breaking syncing - but did anyone actually
test this when FC4 was in development. I doubt it, it seems to me that
this rather major regression was discovered post release. We need to get
more people testing rawhide to ensure that such bugs do not go unnoticed
and that people don't just shrug them off thinking, someone else will
discover this or the developers probably already know about this.

I felt that way about this cute little bug in rpm a while back that
completely broke it by default on my setup because of my locale
defaults[1], I mean I'm clever enough to work around this one but never
the less it's a bug and it's still in there and it has been forever.

I'd be most willing to do a weekly update mail to the devel list
pointing out the user bugs an eventual rawhide testing team is able to
find and confirm, I have plenty of time on my hands and I'm more than
willing to donate it to this effort if there is support for the idea.

David *breaking code in interesting ways since 1981* Nielsen

[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161582

Attachment: signature.asc
Description: Dette er en digitalt underskrevet brevdel

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux