[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[dash-dev] Move from CVS to SVN
|
I was wondering if there is a chance we could migrate the code repositories from CVS to SVN. Besides being the *future* of source code control ;), it would allow me to access the code repositories from behind the firewall here at work. I have already tried the attempted workarounds and they do not function. I am anxious now that Paul made some commits to get my hands dirty and get going.
I would love to propose a set of functions in rapid succession to enhance the Monkey and bring it up to the functionality of my Groovy Monkey tool. Of course I will make the suggestion of the functionality to the group for input (
i.e. up/down/modify approval ) first, but be assured the risks of adding this functionality to the stability of Monkey are minimal. This is true I believe for three reasons. 1. Groovy Monkey is based on an earlier version of Monkey, so since it is not a completely from scratch seperate solution, I think that integration problems will be minimized. 2. Groovy Monkey has been out in the public sphere and used by a number of people already, demonstrating that it is stable. 3. I like to write unit tests for most things that I do.
--
James E. Ervin, IV
A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.
-Robert A. Heinlein