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.
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
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 li
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
