concept of package "ownership"
mschwendt at gmail.com
Sat Jul 3 09:38:27 UTC 2010
On Sat, 03 Jul 2010 03:40:57 +0200, Kevin wrote:
> Thomas Janssen wrote:
> > You have to accept the maintainers decision to not update it yet? What
> > do you think will happen if everyone builds the wishes he has and
> > breaks a lot of stuff with it? Anarchy? We have processes for that in
> > Fedora: https://fedoraproject.org/wiki/MikeKnox/AWOL_Maintainers
> It is part of the Fedora Objectives:
> to "be on the leading edge of free and open source technology". Given that,
> it is completely unacceptable to not upgrade software to the current release
> in Rawhide (within a reasonable timeframe, of course we're all not available
> 24/7) unless there's a really good reason to (in which case that reason
> ought to be given in the bug report asking for the upgrade!), especially
> when upstream is asking for their software to be upgraded.
> So the maintainer's decision (assuming there even WAS a decision rather than
> just lack of time or worse) goes against Fedora's Objectives and so it's not
> OK to say that it should just get accepted.
> We should really be more aggressive about allowing to upgrade other people's
> packages in Rawhide if the maintainers don't do it within a reasonable
> timeframe and don't document any good reason not to do the upgrade.
Ridiculous. :( The way you've phrased it doesn't meet the "be excellent"
guidelines IMO. There is nothing "completely unacceptable" or "against
Fedora's objectives" with skipping certain upstream releases. And I hope
that nobody will become "more aggressive" or try to force me (or other
packagers) to upgrade packages. I don't want anyone among the Fedora
contributors to be "aggressive" in any way when talking to me or when
trying to make me do something.
As a user or fellow packager [or upstream developer], you are free to
suggest upgrades in a bugzilla ticket. And hopefully you evaluate the new
release to examine it for changes compared with the previous release in
Fedora, so you can give a rationale for your upgrade request. If you meet
resistance, you'll have to live with that or return with a competent
If you demonstrate interest in the packaged software (and I truly hope
more people will do that), become a maintainer of the packages you want to
upgrade and collaborate with existing maintainers. It *can* be a great
deal of extra fun to see multiple people work on the same packages,
push fixes and updates, communicate with upstream, and experience
More information about the devel