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

Re: RFC: CHANGES

From: Michael Price <mprice_at_atl.lmco.com>
Date: 2003-02-19 18:52:47 CET

cmpilato@collab.net writes:
> > Anyone wise in the ways of dist.sh-foo who has a free moment please let
> > me know.
>
> Whatcha need?

Well, my impression of the first few commits was as follows:

  1. Get the go ahead to bump the version number and commit CHANGES.
  2. Copy HEAD to branches/0.18
  3. Use dist.sh to create the tarball.
  4. Fix bugs on branch.
  5. Go back to step 3 as needed.
  6. Merge relevant changes to trunk if needed.
  7. Copy branches/0.18 to tags/0.18.
  8. Remove branch if its no longer needed.

So, when I'm running dist.sh, if I specify the branch (branches/0.18) as
the REPOS-PATH then do I specify the VERSION from the commit in #1 above
or do I use some other revision number?

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 19 18:55:14 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.