[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.5.0-alpha2 tarballs up for signing/testing

From: David Glasser <glasser_at_davidglasser.net>
Date: Fri, 29 Feb 2008 19:42:02 -0800

On Fri, Feb 29, 2008 at 7:22 PM, Karl Fogel <kfogel_at_red-bean.com> wrote:
> "C. Michael Pilato" <cmpilato_at_collab.net> writes:
> >> +1 on pulling in hacking.html and anything else we want to ship with,
> >> but then let's make sure the distro-rolling policy is to explicitly
> >> pull in the *latest* (trunk) versions of the files in question.
> >
> > Just to note a complication with moving 'www' out of trunk: there's
> > an instance set (a bundle of custom logic) on Tigris.org that is
> > responsible for publishing the web pages at subversion.tigris.org from
> > our trunk/www repository directory. Changing this requires some
> > CollabNet Engineering effort, and I'm pretty sure that effort is not
> > the best use of time right now.
>
> I misunderstood the thread, sorry. I was merely assenting to not
> shipping all of 'www' with dists, not to moving it out of trunk.
>
> I like the fact that when you check out the development sources, you
> get the www/ directory -- it emphasizes that they're just source files
> like any others, and that you can patch them like you can patch a C
> file, and that they're part of the developers' collective
> responsibility.
>
> I'd rather just change how we roll dists, but still leave www/ in
> trunk, though I don't feel all that strongly either way.

How about we leave it in trunk but remove it from release branches?

--dave

-- 
David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-01 04:42:15 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.