[arch-dev-public] Possible signoff addendum

Dan McGee dpmcgee at gmail.com
Fri Sep 12 15:09:16 EDT 2008

On Fri, Sep 12, 2008 at 1:39 PM, Thayer Williams <thayer at archlinux.org> wrote:
>> On Tue, 2008-09-02 at 08:02 -0400, Paul Mattal wrote:
>> >
>> > It's not necessarily a bad thing to have the signoffs come from testers
>> > who are not developers-- it saves time for developers to be developing
>> > if others are testing.
>> >
>> > I know I test when I can, but usually get around to it less when I have
>> > a backlog of developing to do already.
> I would be happy to test more packages, but I am hesitant to open up the
> testing repo on my system after having some bad encounters in the past.
> I've also got an arch in virtualbox, but that doesn't really help for
> hardware-related stuff like the recent 3945 wifi update.
> How do you other devs manage your test packages? Do you use separate test
> machines or are ya just livin' on the edge? Any best practises you'd like
> to share?

Testing hasn't broken my machine beyond a quick 5 minute fix once in
the last 6 months. I think we are getting a lot better at self-testing
before blindly pushing packages. It isn't like you have to -Syu every
day either- just take a glance at the ML and see if there are any "OMG
broken" messages there before upgrading.


More information about the arch-dev-public mailing list