Robert Collins <robe...@robertcollins.net> (20/12/2009):
> > If you:
> >  - start doing some QA checks before uploading your package;
> 
> I already do such checks.

I'm wondering how the obviously missing B-D went unnoticed then. I
thought checking ones package builds fine in a clean chroot was
supposed to be on everyone's list. But oh well, call me an elitist or
something.

> >  - start checking your package builds fine on the buildds;
> 
> I work in an event driven fashion, so I don't plan to do this, and I
> don't think its a reasonable thing to ask for either. Polling is
> inefficient and a waste of peoples time.

Oh, if having a quick look on the buildd page to check everything
looks in order is overkill, I guess you're relying on your pre-upload
build check, then?

> >  - start doing what you have to do (cf. above) to get bug mail;
> 
> I will look into this; OTOH bug 561549 was open for 2 days - hardly
> the sign of an abandoned or in-distress package.

I'm not sure how those 2 days are related to being subscribed to the
packages one maintains.

> The things you ask for have to do with you not having to speak to
> people, rather than being relaxed when you do. Nevertheless, the
> approach you choose to use with other developers is up to you. I
> find a stressful approach unpleasant and unnecessary. I hope by
> communicating about this a more pleasant environment might arise. We
> are all in this together.

If I hadn't seen so many broken/untested/whatever uploads, I certainly
could be in a more positive mindset when I notice yet another broken
Build-Depends case.

Nonetheless, I have to say I'm quite happy to see people (like you)
fixing things quite quickly after they're reported. What strikes me
everytime is that such uploads happen, and so often.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature

Reply via email to