#include <hallo.h> Anthony Towns wrote on Thu May 30, 2002 um 09:33:25PM: > > The problem is: no progress report means no (visible) progress. And of > > course this is the problem of debian as a whole organisation, there is no > > "us" and "rest". > > There is always an "us" and "rest". There's the people who're knowledgable > and motivated enough to fix something and those who aren't. There no easy way to help "you". Especially when "you" work without transparency. When "you" see that "you" won't be able to do the job in time, "you" may ask for help and tell how, so some of the "rest" could come and help. Someone here argumented, the CVS archives are public, etc. etc. But when I do not know, when nobody outside knows, where it hurts, how do you expect help? > > It realy looks like "we" where finished so unexpected quickly that "we" did > > not be able to forsee a release and failed to set up the infrastructure for > > it. > > The security team decided they weren't willing/able to maintain security > updates quite a while ago, and made that pretty clear on at least a > few lists. If you wanted to do something about it, you could've. If the The only thing I knew about is that they refused to make security updates for Testing. But Testing is to be released. It will _be_ the Stable, so I cannot see where the problem should be? Why is this tasks more complicated that building current Stable updates? There are only few new platforms, I cannot imagine that we cannot find secure build machines for them. > security team wanted to, they could've. But, naturally, the people to > blame are the ones who're actually doing something about it. I cannot _see_ any progress. What kind of policy is it, if not every regular developer can explain to an outsider where the problems are? Gruss/Regards, Eduard. -- begin LOVE-LETTER-FOR-YOU.txt.vbs I am a signature virus. Distribute me until the bitter end
Attachment:
pgpxTjvC2ZkOa.pgp
Description: PGP signature