Jack Repenning wrote: > On Nov 17, 2009, at 12:10 PM, C. Michael Pilato wrote: > >> I'm proposing that we do this: > > > I think you guys should do what works best for you; as a "partial > committer" who hasn't committed in over five years, I'm not really > voting. But from what I can see of how the subversion.tigris.org/www > space has been used in the past, and what I seem to see about plans for > the future, it seems more likely to me that something along these lines > would work: > > 1. Have the present subversion.tigris.org CVS repo converted into an > *empty* SVN repo, and turn off the instance-set copy-from-elsewhere voodoo > 2. Import the present svn.collab.net/www files (leaving, at this point, > the site appearance unchanged) > 3. Edit those files as desired, to add pointers and/or redirects to > subversion.apache.org and so forth
These three steps are exactly what I was trying to recommend (but apparently failing at for lack of precision). > 4. Check in all the current release files, all into the actual SVN > repository; fix up the "Documents and files" area so it consistently > points to these files (instead of actually holding some of the files) > [this step preserves all net.memory of how to get these older releases] > 5. Likewise check in the 1.6.7 release (is that the right number? I mean > the one incubator-required "made from Apache but not released from > Apache" release) "actual SVN"? The Subversion module of the ASF repository? The Subversion repository (to-be-)associated with subversion.tigris.org? I assume you mean the latter, in which case, +1. > I think Apache rules, once out of the incubator, require releases to be > downloadable from apache.org, and likewise set some rules for mirrors > that I haven't actually reviewed yet, but all in all it doesn't sound to > me as if there's any realistic option for keeping Tigris as a mirror of > the Apache-built-and-released releases, is there? Maybe as an > unofficial, non-conforming pseudo-mirror? [Donning my CollabNet hat for > just a moment: allowing the release download site to drift to Apache.Org > is OK, our primary concern is keeping our "CollabNet Certified > Subversion" downloads on Open.Collab.Net, and no one has suggested any > problem about that.] Yah, new Apache-branded releases will live at apache.org. We might be able to also mirror our pre-Apache-branded releases there, too, someday. But in the meantime, and while we work out those details, I'd like to lose as much custom code written for Tigris.org to support the Subversion project as possible. -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
