Re: [Exist-open] [Exist-development] [HEADS-UP] We have moved to GitHub

[Dannes W. <di...@ex...>]

On 28 Jul 2013, at 16:49 , Eric Palmer <er...@er...> wrote:

> This is very cool and very welcomed.   I use git daily and think this is a very good move.
> 
> Can we assume that the svn repo will stay up for some time?

the sf.net svn-repo is still there, but in the current state, it looks empty; a specific revision-id should be applied to retrieve the correct version from 'trunk'. 


> I have ansible scripts (ansiblework.com) that install exist on amazon ec2 instances and will convert this to doing so from git.  However I may not convert over to git for a couple of weeks are we are in the final planning phase to go live with a new public site with exist-db as the backend.  Too many other things to work on before go live.

so it is possible, but with some additional svn parameters


> 
> In consideration of this statement in the readme file
> Note In the above example, we switch the checked out branch of eXist from "develop" to "master". We are making use of GitFlow for eXist, and as such "develop" is our current stable work in progress which will eventually become the next release version, whereas "master" is always the last released version. The choice of which to use is entirely yours.
> 
> Will there be a way to clone a specific version of exist-db via git?  Will you tag versions and push the tags or will this ability not be there?  Also is there a file in the repo that contains the lastest version that is easily parsed

it should be possible to clone a specific version from git, you'd need to use a specific hash for a specific branch. I'd say you need to have a hash from the 'master' (aka stable) branch.....

cheers

Dannes