Re: Subversion 1.7

[TheDO Webmaster]

The Subversion binary is embedded in Versions. A new release of Versions is
required to get the latest Subversion.

1.7 is backwards compatible with earlier versions, so there should be no
compatibility issues.

Release Notes:
http://subversion.apache.org/docs/release-notes/1.7.html

/TheDO/


On Mon, Oct 17, 2011 at 3:35 PM, Alex Zavatone alexzavat...@gmail.comwrote:

 Does this mean that Subversion currently does NOT support SVN 1.7?

 On Oct 17, 2011, at 3:52 PM, hputman wrote:

  What's the plan for upgrading to subversion 1.7 in Versions?
 
  --
  You received this message because you are subscribed to the Google Groups
 Versions group.
  To post to this group, send email to versions@googlegroups.com.
  To unsubscribe from this group, send email to
 versions+unsubscr...@googlegroups.com.
  For more options, visit this group at
 http://groups.google.com/group/versions?hl=en.
 

 --
 You received this message because you are subscribed to the Google Groups
 Versions group.
 To post to this group, send email to versions@googlegroups.com.
 To unsubscribe from this group, send email to
 versions+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/versions?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Versions group.
To post to this group, send email to versions@googlegroups.com.
To unsubscribe from this group, send email to 
versions+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en.

Re: The architecture of versions installation

[TheDO Webmaster]

You'll be happier using a distributed version control system, such as Git. I
recently switched my company to Git earlier this year and have never looked
back. So much better and less problematic managing repositories. Dead easy
to create a repository on any box and have clones on any other box.
Push-pull between them. I used to be a die-hard Subversion fan.

/TheDO/

On Thu, Sep 8, 2011 at 7:14 AM, Imaje shwiin...@googlemail.com wrote:

 Hello,

 I am tasking myself to get into Versions in order to improve our
 workflow for our small two-man team however, I cannot get my head
 around how the setup and architecture of versions and our existing
 systems.

 At the moment, we have a server which we work off, all the sites we
 develop are kept on a local server which myself and one other access
 when working on projects. These local versions are then deployed onto
 our remote server.

 I have been exploring Versions and also beanstalk, however I don't
 want to store our sites online, I want to keep everything as local as
 possible before deployment.

 So in a nutshell, I am looking to use versions to help manage our
 sites locally. and also to manage sites after deployment like so.

 Developer (local) -- Local Server  Remote
 (Live site) Server

 Can versions use a local repository - but (when satisfied that
 development is complete) Commit the site to remote server?

 I hope I'm making sense.
 Many thanks for your help.

 --
 You received this message because you are subscribed to the Google Groups
 Versions group.
 To post to this group, send email to versions@googlegroups.com.
 To unsubscribe from this group, send email to
 versions+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/versions?hl=en.



-- 
You received this message because you are subscribed to the Google Groups 
Versions group.
To post to this group, send email to versions@googlegroups.com.
To unsubscribe from this group, send email to 
versions+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/versions?hl=en.