on 4/15/00 5:02 PM, Chris Meyer <[EMAIL PROTECTED]> wrote: > Thanks for pointing this out. Like I said, I'm relatively new to this > whole open source experience and I still have a lot to learn and any > mentoring is helpful. Cool. Also, don't take any of my posts as negative against you. I am willing to help you learn about OS as much as I can, I just don't have all the time in the world to teach you. ;-) > I've been assuming that the readers of this list are developers who are > interested in working out the code and discussing various changes. To this > end I think submitting patches is a nice way to go about proposing and > discussing a change. Even with write access into the repository, it might > be a good habit to continue. In that way developers like myself could > submit changes with a large potential affect without jeopardizing the core > CVS system and when the change was approved the original author or else > someone with CVS write access could merge the changes. CVS branches could > also be used for this. Please let me know where my assumptions are > incorrect. Right, a branch could also be used. Patches tend to be better as branches can be a pain to manage. I'm willing to give you write access as soon as I can trust that you won't commit something that will require hundreds of thousands of lines of code in projects all over the world to change. ;-) > On another note, has anyone spent any time thinking about or developing a > test suite for ensuring that key functionality remains in the system? This > may be able to mitigate the affects of changes that developers like myself > make to the system. Time? Who has time? ;-) I agree, this would be great. I would use Watchdog to develop a set of tests. <http://jakarta.apache.org/watchdog/> -jon -- Scarab - Java Servlet Based - Open Source Bug/Issue Tracking System <http://scarab.tigris.org/> ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
