Re: svn commit: r21807 - in branches/1.4.x: . contrib/client-side www/merge-tracking

[David Glasser <gl...@mit.edu>]

On 10/6/06, dlr@tigris.org <dl...@tigris.org> wrote:
> Author: dlr
> Date: Fri Oct  6 10:37:43 2006
> New Revision: 21807
>
> Log:
> Merge r21575 from trunk into the 1.4.x branch, updating the URL for
> the svnmerge.py wiki page.

Should we be in general merging everything from www into the backport
branch?  It seems odd to ship releases with old versions of the
website, the FAQ, etc.  I'm not sure if many people actually look at
the www in the distribution, though.

(There are probably a bunch of other non-code things that should
probably get backported, like COMMITTERS, etc.  That doesn't require
voting, right?)

--dave

-- 
David Glasser | glasser@mit.edu | http://www.davidglasser.net/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: svn commit: r21807 - in branches/1.4.x: . contrib/client-side www/merge-tracking

[Daniel Rall <dl...@collab.net>]

On Fri, 06 Oct 2006, David Glasser wrote:

> On 10/6/06, dlr@tigris.org <dl...@tigris.org> wrote:
> >Author: dlr
> >Date: Fri Oct  6 10:37:43 2006
> >New Revision: 21807
> >
> >Log:
> >Merge r21575 from trunk into the 1.4.x branch, updating the URL for
> >the svnmerge.py wiki page.
> 
> Should we be in general merging everything from www into the backport
> branch?  It seems odd to ship releases with old versions of the
> website, the FAQ, etc.  I'm not sure if many people actually look at
> the www in the distribution, though.
> 
> (There are probably a bunch of other non-code things that should
> probably get backported, like COMMITTERS, etc.  That doesn't require
> voting, right?)

The release process document [1] doesn't seem to mention this, but I
seem to recall us doing something similar in the past...?

[1] http://subversion.tigris.org/release-process.html