Ready for new RPM version?

[Ben Boeckel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jesse Keating wrote:

> On Fri, 2009-02-27 at 16:39 -0500, Jeremy Katz wrote:
>> That said, I've been running rawhide on basically all of my boxes all
>> the time without a need for a reinstall[1] for a decade later this
>> year!
>> :-)
> 
> and the counter example is trying to run rawhide, have a day without
> email working.  Have a day without the system booting, have a day
> without the wireless working, so on and so forth.  Those days add up
> quickly when it's your critical functionality that breaks.
> 
> Making it harder to make those things break just means we wind up with
> rawhide, and rawerhide where the real changes are made, and the whole
> process repeats itself.
> 
> Sure, I'd love more people to use rawhide, and I'd love rawhide to break
> less often, but you're not going to win any favors by convincing
> developers to use rawhide and then not hear from them for a few days
> because all their communication software just broke.
> 

Maybe we should encourage (NOT require) maintainers to dual boot or use 
older machines to test rawhide out with on a weekly basis or something. 
Obviously not everyone has the time or hardware, but I was pleasantly 
surprised that 802.1x Just Worked™ with Network Manager for once. If 
anything, it would keep people more in-tune with what is coming down the 
tubes and alert to problems that may arise from things being pushed to 
earlier releases and other possible breakage. If some problems (like the 
gcc-4.4 rebuild failures) had been caught by at least some maintainers 
before reading the ML, turn around time may have decreased. Thoughts? 
Overall, keeping rawhide fast-paced, but decreasing time between breakage 
and fixing would be a big improvement (rather than testers -> bugzilla -> 
discussion -> fix, just test -> fix).

- --Ben

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkmod0cACgkQiPi+MRHG3qQhvACeJ6OS11MXMg/6tppUeJIQ0oJG
gFMAnju3RlHifNel8g1XqMkYGs+Bhq6i
=GMVf
-----END PGP SIGNATURE-----