[Swift-devel] Swift application testing practices

[Mike Wilde]

First, lets change this subject line.

Second, I'm learning that we really are an open source development 
team, in that we're very distributed.  And on such teams, we need to 
learn how to dish out and receive scoldings from each other. Both 
with a smile.  Like so:  :)

This discussion is good and the kind of pointers we need to exchange 
as part of continuous improvement.

Nika, it sounds like its a simple case of using a different 
procedure to update your Swift code - and that we should document 
the procedure for all to use, especially the growing user base.

I'd like to see us starting and growing nice wiki pages for these 
techniques, and to periodically restructure the wiki as needed to 
keep it informative and useful to us.

Please, do this as a matter of course, without being "assigned" to 
do it. It helps makes our environment a great place to work, and 
certainly helps us grow.

Btw - I found the talk by Brian Fitzpatrick at the Globus committers 
meeting to be excellent, and very inspiring.  Dont be misled by the 
title: it applies as much to defining what "Good" people are as it 
does to dealing with "bad" ones.

Here's a nice summary:

http://www.oreillynet.com/conferences/blog/2006/07/oscon_how_open_source_projects.html

The video is at:

http://video.google.com/videoplay?docid=-4216011961522818645

The slides are at:

http://www.slideshare.net/vishnu/how-to-protect-yourhow-to-protect-your-open-source-project-from-poisonous-people/

And a great book recommended by both the speakers and our own Ben is:

Producing  Open Source Software
How to Run a Successful Free Software Project
by Karl Fogel

Full text is at:
http://producingoss.com/

This is a nice fast read that you can get a lot out of on each 
10-minute break that you spend browsing it.

I think there's loads of things we can pick up from here to help us 
grow as a project and as a team.

- Mike



Veronika Nefedova wrote, On 6/19/2007 7:18 PM:
> I do not think its a correct asessment.
> 
> I did update *many* times along the course of last couple of weeks, I 
> just didn't recompile my dtm files. And they worked just fine, btw.
> I do not know how it happened that I ended up with the old version of 
> swfit script -- it might've happened during those submit host-to-submit 
> host moves, and obviously it was not intentional to discard any new bug 
> fixes.
> 
> Nika
> 
> On Jun 19, 2007, at 7:10 PM, Ben Clifford wrote:
> 
>>
>>
>> On Tue, 19 Jun 2007, Mike Wilde wrote:
>>
>>> So, at a practical level, what went wrong here and what do we do to 
>>> correct
>>> it?
>>
>>> - use only official builds if at all possible (unless you need to
>>> include a fix thats not yet been included in a build?)
>>
>> there's a reluctance on Nika's part to upgrade I think because its a
>> hassle for her to get the Falkon/cog provider into a new build. It should
>> not be hard. provider-deef should be going into SVN 'real soon' (i.e. as
>> soon as Yong provides a clean recent tree for me to import) and after 
>> that
>> it should be a lot easier to deploy the most recent swift + most recent
>> provider-deef.
>>
>> --_______________________________________________
>> Swift-devel mailing list
>> Swift-devel at ci.uchicago.edu
>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>
> 
> 

-- 
Mike Wilde
Computation Institute, University of Chicago
Math & Computer Science Division
Argonne National Laboratory
Argonne, IL   60439    USA
tel 630-252-7497 fax 630-252-1997