• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Site management strategies with Subversion
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Site management strategies with Subversion


  • Subject: Re: Site management strategies with Subversion
  • From: Zak Burke <email@hidden>
  • Date: Mon, 13 Mar 2006 18:05:20 -0500

email@hidden wrote on 3/13/06 4:53 PM:
Thanks, Zak. I follow you, but I'm still confused about one thing. How are you creating the source directory, the one being accessed by APP in your release.sh script?

I haven't made the leap to Svn so I have no idea how this would work (or not) in that world. Here is what I do:


	cd /path/to/some-committed-build-directory
	cvs tag 1-0-4 .

	cd /path/to/some-release-directory
	cvs export -r 1-0-4 some_app -d some_app-1-0-4
	cd some_app-1-0-4
	ant build
	/usr/local/bin/release.sh some_app.woa 1-0-4

In the CVS world, one could tag and then export, like you said, and you might tag only a subset of the files that have actually been committed since the last release.

When I tag for a release, I tag the whole tree, not just the files that have changed since the last release. Given the tagging process you've described, I'm not sure my process works with your release style.


Is it possible to follow the process you're describing and yet not include the changes made to a particular framework?

You can tag individual files, or use rtag to tag the repository as of some date besides the present.


It appears that in Subversion that's not possible unless the code for a project is broken up into multiple repositories, one for each logical unit. Maybe that's the right thing to do?

That's how I've done it. Each library and app is a separate module.

Best,

zak.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Site management strategies with Subversion
      • From: email@hidden
References: 
 >Site management strategies with Subversion (From: email@hidden)
 >Re: Site management strategies with Subversion (From: Zak Burke <email@hidden>)
 >Re: Site management strategies with Subversion (From: email@hidden)

  • Prev by Date: Re: Site management strategies with Subversion
  • Next by Date: Re: Thoughts on choosing a source code control system?
  • Previous by thread: Re: Site management strategies with Subversion
  • Next by thread: Re: Site management strategies with Subversion
  • Index(es):
    • Date
    • Thread