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

Re: Upcoming release 0.25.

From: <kfogel_at_collab.net>
Date: 2003-07-04 05:37:05 CEST

Paul L Lussier <pll@lanminds.com> writes:
> First, does this really mean 'branch' or does this mean 'tag'?
> There doesn't seem to be anything under svn/branches which looks
> like a previous release, but svn/tags definitely looks like
> what I want...

Read the release process from start to finish, and you'll see a step
(8) where the branch gets moved to become a tag :-).

Also would strongly suggest using 'svn log' to explore the things
Michael Price has done on his release branches. All the history's
right there, might as well use it...

> - make sure the working copy contains apr, apr-util, neon, and the
> Docbook tools (XSL, FOP). Those are all needed to build a
> distribution.
> I have these in my current working copy. However, I don't
> remember where/when/how they got there. I also haven't really
> built svn from my wc other than building the docs on occasion.

Michael could best answer where he gets these from, if it's not
obvious from looking at your working copy and/or the various README
and INSTALL files in the Subversion tree.

> Are these also under svn control available for checkout (maybe
> by using svn:externals or something? Or, do I just need to go
> and grab the latest versions of all these sources?
> (another thing I'd like to add to the release docs)

They're not under svn control.

Keep asking -- Questions Are Good :-).


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 4 06:27:31 2003

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.