On Mar 11, 2008, at 12:40 PM, Andrew Petro wrote:
+1 for #2. Short term pain. Slightly longer term simplicity. Simplicity is good.
-1 for #2. For me the question is more what is the implied contract behind a tag. In the same way that "cool URIs don't change" I don't think tags once created should change either.
+1 for #1 with the suggestion that we remove the trunk & all branches in the up2/ tree and replace it with a README file explaining that the recent source has moved and the existing tags are only there for archival purposes, in addition to locking the tree for commits.
Jason -- Jason Shao Director of Open Source Solutions CampusEAI Consortium 1940 East 6th Street, 11th Floor Cleveland, OH 44114 Tel: 216.589.9626x249 Fax: 216.589.9639 -- Join your friends and colleagues at JA-SIG 2008 - "Higher Education Solutions: The Community Source Way!" April 27th - 30th, 2008 in St. Paul, Minnesota USA Featuring CAS, DSpace, Fedora, Fluid, Internet2, Kuali, Sakai, uPortal, and more! Information/Registration at: http://www.ja-sig.org/conferences/08spring/index.html Subscribe to the conference blog, The Community Source Way http://jasig2008.blogspot.com, for news and updates about the event. Join the Conference networking site at http://ja-sigspring08.crowdvine.com/ You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
