I have http://svn.apache.org/repos/asf/lucene/java/trunk/ and http://svn.apache.org/repos/asf/lucene/java/tags/ checked out.
I think having all this "back_compat" folders, under the "tags" can be very confusing, especially for someone who looks in "tags" in search of a released version and finds all the "back_compat" folders not knowing what they mean (there is more "back_compat" folders than actually release tags!) If we are using "tags" for back-compat testing, aren't we overloading the meaning of the "tags" folder? I prefer to see "tags" used for what it is, a place to park an actually released; it shouldn't be used for testing or its content changed dynamically. -- George -----Original Message----- From: Chris Hostetter [mailto:[email protected]] Sent: Tuesday, January 05, 2010 3:21 PM To: [email protected] Subject: Re: "back_compat" folders in tags when I SVN update : Why do I see \java\tags\lucene_*_back_compat_tests_2009*\ directories (well : over 100 so far) when I SVN update? Are you saying you have "http://svn.apache.org/repos/asf/lucene/java/"; checked out in it's entirety? That seems ... problematic. New tags/branches could be created at anytime -- it's even possibly to have Hudson autotag every build if we wanted. Server side these tags are essentially "free" but if you checkout at the top level you pay the price of local storage on update. I would rethink your checkout strategy. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
