Jonathan wrote:
CVS maintains an internal revision number. What I have done is commit fairly often, which effectively provides a backup of my work. Then, when I am ready to release a patch, I tag all the files with that patch number. I don't use the internal CVS numbers > for anything.
OK that works for me. The one caveat is now that I am committing, we both need to be sure that our commits compile and (more or less) work. This isn't an issue when working by ourself. I am cleaning out all emails from the scrolling credit screen and bringing it up to date. The one exception are Jonathan's and my emails using the fractint.org domain. I think I should delete all addresses also. At one time I used to joke that Fractint's main function was as an address/phone book of the developers. But with current privacy/SPAM concerns, our old style is probably not good. Besides nearly all the information is out of date. I must say it gave me a strange feeling to edit the long list of contributors. Fractint's "Stone Soup" development model was certainly an interesting historical phenomenon in it's time, even if archaic by today's open source standards. If anyone currently has their address or email in Fractint and would like to keep it there, let me know. An example might be if you are still selling CDs of fractals. Tim