Re: Bug#340462: gtk-gnutella: version in stable is too old for the network - upload to volatile
Hi Anand,
> Again, it'd be more constructive if your emails weren't always full of
> small, personal, jabs (e.g. "I hoped that you might get more cooled down ...
> I'm sorry that I was wrong".)
please read
http://lists.debian.org/debian-volatile/2006/01/msg00007.html again. It
has been told you several times why we WONT accept gtk-gnutella the way
YOU proposed to have it in volatile. Also you have been told, what to do
to get a new version of your package into volatile.
> > As most of the readers might have noticed, we (the volatile team)
> > usually respond quite fast to good ideas
>
> Perhaps. I'll leave what other readers decide or notice up to them. The
> mailing list archives are a great testament to the speed of the volatile
> group responses, and I'm sure readers don't need either of us to point out
> length of time between maintainer requests and your responses.
Actually, i am tired of this kinds of lies. My initial response on your
question about getting gtk-gnutella into volatile was less than a day!
(http://lists.debian.org/debian-volatile/2005/11/msg00021.html and
http://lists.debian.org/debian-volatile/2005/11/msg00022.html)
That there were some mails from you on which i was a bit "offended" of
is another point. I thought of shutinging down volatile at all at this
point several times. So i decided to wait a bit with the answer for
myself to calm down.
> I did, briefly, consider asking either you or the technical committee to
> reconsider but I have come to the conclusion that volatile is a
> technical hack around a (perceived) social problem: that it is hard to
> get non-security related updates into stable.
>
> I believe it is more important to address that directly rather than spending
> time working around the issue and further balkanising Debian into teams
> who need to defend their 'turf'.
Yes, this is more or less what volatile is about. If you have an idea
how to solve this problem, please speak with us and the community. We
would not have volatile if we would not have this kind of "social
problem" of getting non-security related updates into stable.
I am open to new ideas, but i also have my own ideas how the volatile
service should work. I think we (at the volatile team) share this ideas
and have a consensus about it. That is one of the reason why we
(Andreas, Marc, Philipe and I) told you several times what to do.
Greetings
Martin
Reply to: