On Sun, Mar 07, 2010 at 12:03:57PM +0100, Michael Schwendt wrote: > My reason to comment on those threads on devel list is really just that I > want to retain the freedom to decide when my updates are ready to be > released. I'm responsible for giving them adequate testing. Users > expect the packager not to release broken crap. I don't want to wait for > +N karma that previous updates haven't gotten either while new bugzilla > tickets have shown that a problem *is* affecting N>1 users. > If there are technical requirements for an update to make a temporary halt > in updates-testing for a day, e.g. for scripts to be run (and mind you, > repoclosure is run on updates-testing, too), fine. I can live with that. > Just no silly rules, please, such as arbitrary "autoqa"-scripts getting > veto powers to block updates, if perhaps rpmlint complains about a spec > file. No experiments, please, just because some packagers are upgrade-mad. > +1 > > When version X of a software is supported in F-12, the same version X > > can be supported most of the time in F-11. And if it can be supported, > > it should be supported. > > "Can be supported" as in "if it builds, push it as an upgrade"? > Wishful thinking. This is exactly why Fedora releases are _not_ supported > for two years or more. Most package maintainers ought to focus on one > dist release (at most two), as their daily usage only covers one dist, > too. [The exception being those packagers who *really* run some software > on multiple dist releases in the same way.] > One problem I'm finding here is that we've suddenly exploded the number of releases we care about updating in the normal bugfix case. Currently, F-14, F-13, and F-12. As you say, typical developers can really only test on one of those because they're doing their daily work on only one. Rawhide has traditionally had a lack of developers running it so we could say it's no worse than normal. F-13, OTOH is being pushed as something for people to actually run if they want a more adventurous update style. That means developers who run F-13 won't be testing their updates to F-12 anymore and developers running F-12 won't be testing their updates for the people consuming F-13.... I think this is something we should be thinking about as we push these discussions forward. -Toshio
Attachment:
pgpxZEs0Xgste.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
