[csw-maintainers] testing team for packages

[Gary Law]

2009/1/21 Philip Brown <phil at bolthole.com>

> On Mon, Jan 19, 2009 at 01:11:55AM +0100, Peter Bonivart wrote:
> >...
> > Not only will maintainers know better what is and is not
> > happening with their packages, I think it will encourage testing as
> > well.
>
> a side note: maintainers already tend to "know what is happening" with
> their packages already. Often within a few hours; usually within a day.
>
> As far as testing goes:
> Across-the-board testing doesnt happen because people write a fancy
> interface.
> Testing happens only when people *commit* to spending a WHOOLE bunch of
> their own time to do so.
>
> I think it makes sense that when, and IF, people step up to doing testing,
> that *those* people should get to design the interface they are going to
> use.
>
> Contrariwise, if no-one is willing to commit to doing testing, it makes no
> sense to spend a bunch of time designing an interface that no-one is going
> to use.
> If someone does decide to volunteer to test in the future, they may well
> toss it out the window and write their own. So it's waste of time and
> effort to write one now, before someone commits to doing testing.
>

People test my packages before release. I get feedback and I've made plenty
of changes in response to this. Most of this came from you Phil, but I got a
lot from other people too, including one report only last week from the
package I rolled up a week before.

An entirely or largely automated test regime would reduce or eliminate the
load on volunteers of course.

Gary



-- 
Gary Law
Email: garylaw at garylaw.net
Chat googletalk/messenger: gary.law at gmail.com
iChat/jabber/AIM: gary.law at mac.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20090121/45ee6399/attachment.html>