Its a busy day here at the Its About Bloody Time Dept. Test::More's repository is now publicly available. That's the good news.
The bad news is its Aegis which most of you have probably never used. The good news is it has a very good web interface. http://mungus.schwern.org/cgi-bin/aeget .1.49 is the currently active branch. .1 would contain what I just uploaded as 0.48_02 but I have to write some scripts to make partial branch merging less tedious. You can see what's been done since 0.48_01 here: http://mungus.schwern.org/cgi-bin/aeget/Test-Simple.1.49/@@[EMAIL PROTECTED] And what I've got waiting to do here: http://mungus.schwern.org/cgi-bin/aeget/Test-Simple.1.49/@@[EMAIL PROTECTED]@completed Downloading the most current version as a tarball is currently a little backwards. You have to go up to .1 and into the .49 change and then download. http://mungus.schwern.org/cgi-bin/aeget/Test-Simple.1.C49/@@[EMAIL PROTECTED] Using Aegis for Test::More has been an experiment. I like the features of Aegis, the change sets, review process, enforced testing, etc... and wanted to see if I could apply this to Open Source development to easily allow anyone to work as a full fledged developer. So rather than submitting a patch anyone could have access to the repository. This is ok because in the Aegis world, developers cannot fully commit a change until it has been reviewed and integrated. Myself and a few trusted folks would be reviewers and I would be the sole intergrator with final say. It all works great IF, and this is a big if, you're all working on the same filesystem. Aegis lacks a real networking model and the only way to use it on more than one machine is either a distributed file system or to shuffle around aedist files which are little pieces of the repository. As you can imagine it very rapidly becomes cumbersome. So in this respect I consider the Aegis experiment a failure. However, if you're working on one machine its great. If anyone wants Developer access to the repository let me know and I'll set you up with an account on mungus, access to Aegis and a short developer's tutorial (its no where near as complex as the Aegis user guide makes it look). If this works out I might do the same for MakeMaker and other important modules. There's also a way to have Aegis produce a mirrored CVS repository, I might set that up, too. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/ If at first you don't succeed, call in an air strike.
