On Nov 17, 2009, at 2:31 PM, C. Michael Pilato wrote: > Mark Phippard wrote: >> On Tue, Nov 17, 2009 at 3:10 PM, C. Michael Pilato <cmpil...@collab.net> >> wrote: >> >>> * Ask CollabNet Ops to remove or disable the instance set that tells >>> the server to pull www bits from svn.collab.net, and let the default >>> behavior (of auto-publishing the /trunk/www directory of the on-site >>> project repository) kick in. Of course, in the process, we'll be >>> careful *not* to lose our 'downloads'/'tarballs' folder (which isn't >>> versioned). >> >> Even though it will be a P.I.T.A for anyone that checks out /trunk/www >> without using sparse directories, should we also import the downloads >> folder into the repos? If we do not do that then this is another >> "special" thing that Ops has to remember. We already accidentally >> deleted this once earlier this year when a security release was posted >> and I asked Ops to manually refresh the web site. > > I've definitely considered suggesting that in the past. I balked at it > before because we didn't have sparse checkouts or because it would be cruel > to expect everyone to start using them. > > Now, I think that would be fine. First, sparse checkouts have been around a > while and are easy to use. But more importantly, I don't expect many folks > would bother checking out this new repository anyway. I mean, a few of us > are going to massage the website into pointers elsewhere for the most part. > If it's up to me, I'll be making heavy use of <meta>-based redirects to the > Apache website.
So, put the tarballs in the old s.t.o repo, not in our shiney asf repo? I've no objection to that, since only a small number of folks are going to be using the old s.t.o, and we've got sparse checkouts (and this would force me learn to use them :) -Hyrum PS - Dear CN Ops, I apologize in advance for schlepping s.t.o/downloads to my local box as I write this.
