> These two points have one common solution - SVN repository with public > reading only. I really want to have control over all modifications by > many reasons. So, I still have complete control over modifications, but > distribution of modifications can be very fast.
I think you'd find that the vast majority of users prefer that you have total control! and wouldn't trust the project otherwise. It sounds like the only decision left is whether any history before v38 should be included, and again, that affects you so much more than anyone else, that you should do what suits you best. It sounded from the original question like you were just about to *create* a SVN repository. If you're starting from scratch, it would seem like a lot of extra work to create the history, for what doesn't seem like enough benefit. It seems to me that history going forward would be just fine. But if you already have an existing repository, it wouldn't hurt to use the whole thing. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
