My proposal... switch the online sites from tags to branches. Easy to do. That way we can take advantage of doc fixes. The only risk is if the branch gets documented with features that aren't in the released code. But since branches don't add any new features, doesn't seem like a problem to me.
WILL On 6/27/07, Nathan Bubna <[EMAIL PROTECTED]> wrote:
we need to find some way to get a Wendy Smoak-type person interested in helping out around here. she has far more expertise and patience for build and doc issues than i could ever dream of having... :) anyway, here's my thoughts: - whoever's ready and willing to jump in and do work on the site building/doc stuff will pretty much always get my support for whatever they want to do with it. let them who do the work make the decisions. :) so, +1 to anyone willing to step up and execute their plan to solve this. - that said, don't we have two sections on the site for each project? the little fixes and stuff should always go in the development docs for the project, and these should be based of the trunk or a branch. once there has been a new release, then we tag that release and update the release docs using that tag. if, in the meantime, the X.x release docs online for some project are broken, then c'est la vie. those were the docs for the release. - i'm not keen on the idea of separating the docs from the release cycle. i'd rather see us consider doc upgrades and fixes as worthy of an X.x.x release. - to reiterate: the last two points are my opinions at the moment. i'll happily follow the lead of someone actually doing the work, even if they go a different way. On 6/27/07, Claude Brisson <[EMAIL PROTECTED]> wrote: > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com
