For now, the scripts on velocity.zones use tags (as stated by "svn info" in /export/home/velocity/deploy/releases/velocity-texen-1.0-site), but I wonder if it is the proper choice, since tags are not supposed to evolve... it'd be quite heavy to have to create a new tag each time we correct a bad link.
The way to go would IMO to link online sites to branches, since online sites can be newer than docs included in the last released version. Also, sticking to tags would mean having to issue an "svn switch" for each fix we've got to put online. I can setup this (by svn-switching checkouts) if you consider it appropriate. Claude Le dimanche 24 juin 2007 à 06:51 -0700, Will Glass-Husain a écrit : > Hi, > > I'm fixing the home page for Texen. (bad links). Quick question on > website/svn process, probably for Henning our site guru. > > I'm updating both texen/trunk and texen/branches/Texen-1.0. > > When we rebuild the website, for the "1.0" tree does it use the tag or the > branch? In other words, will the fix show up automatically, or do we need > to release 1.0.1 for this to happen? > > WILL > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
