I assume it's best to create a new mailing list. I suppose I can send out invitations to all the old list members (anyone see any reason not to do that?)
Sounds good to me - I think a new mailing list is the way to go now that we've decided to fork. Can you just move everyone to the new mailing list, instead of having to have people re-subscribe?
The new repo is SVN, not CVS. I'd like to have a hands on libxml coder do the initial check-in. Someone with a fair idea how to migrate from CVS to SVN. Any takers? I figure we need to check in the current stable release as a tag/ and Ross' development version as the current trunk. Sound right?
SVN sounds good. I guess the question is if anyone wants to migrate the old history from CVS to SVN. If no, then a checkin would be simple. If yes, then someone will have to dig into how that works (I don't know myself, but would hope its not too hard).
Charlie
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ libxml-devel mailing list libxml-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/libxml-devel
