Tags:
definition1Add my vote for this tag development2Add my vote for this tag version_control2Add my vote for this tag create new tag
, view all tags

SVN

Shorthand for Subversion. See Wikipedia:Subversion

From http://subversion.tigris.org/ : The goal of the Subversion project is to build a version control system that is a compelling replacement for CVS in the open source community

TWiki's SVN is browsable at http://svn.twiki.org/svn/twiki/

The TWiki source is now managed in the TWiki Subversion repository. See also SubversionReadme.

  • Get bleeding edge KampalaRelease version and all plugin using Subversion:
    svn co http://svn.twiki.org/svn/twiki/trunk
  • Get current production version (TWiki-6.0.2) with latest urgent fixes using Subversion:
    svn co http://svn.twiki.org/svn/twiki/branches/TWikiRelease06x00

General background on Subversion: Version Control with Subversion (User Manual)

Discussions

This is my way to set up a local SubversionMirrorSetUp in order to add my own branches and changes not compatible with the rest of the world.

-- OliverKrueger - 01 Mar 2006

i'd recommend SVK to do that (as a side benefit, performing an svk update with twiki.org on an empty update takes only a few seconds, as compared what is normally a minute or more using svn update)

-- WillNorris - 01 Mar 2006

MergingInSubversion

-- MartinCleaver - 06 Mar 2006

At the risk of starting another branch war.. can we have a "stable" branch? Which means, a way to checkout the latest stable version of the software, from a URL that doesn't change.

This is useful for those of us that have a SubversionBasedTWikiInstall but want to have the latest stable+patches instead of the bleeding edge, without having to svn switch after each release.

-- RafaelAlvarez - 08 Oct 2006

Now that I think about it, the trick can be done at Apache level. For example, point

http://svn.twiki.org/svn/twiki/branches/Patch04x00

and

http://svn.twiki.org/svn/twiki/branches/STABLE

to the Patch branch, and update it acordingly when a new patch branch is released.

-- RafaelAlvarez - 08 Oct 2006

Rafael, no, not that way smile

I keep intending to create a latest release branch, into which i want to commit the contents of each release zip file. It will take a bit, as you have to make sure that the removed files also are svn removed, but this will be a massive improvement to the build system, as atm you have to change teh build.pl script whenever there is a release (so that it can create the ,v files as incremental changes from the last full release)

-- SvenDowideit - 09 Oct 2006

Rafael. If you use the Patch branch then it only "changes name" when TWiki is released as minor and major version. And this happens 1-2 times per year. When the release is a minor or major there can be some settings and tailoring that gets wiped out so it would be a really bad idea to automatically update a running production site from for example 4.1 to 4.2 or even 5.0. That would have to happen in a controlled way and probably with some hours of work getting your site back in order. But the patch releases in between should always be upgradeable without work afterwards.

-- KennethLavrsen - 09 Oct 2006

We have moved the MAIN development branch to the more standard twiki/trunk location

-- SvenDowideit - 17 Feb 2008

Edit | Attach | Watch | Print version | History: r19 < r18 < r17 < r16 < r15 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r19 - 2010-05-29 - PeterThoeny
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.