[imp] Upgrade question

[Michael M Slusarz]

Quoting Gary Smith <gary.smith at holdstead.com>:

> Looking at GIT, it appears that it will drop the files pretty much  
> the same way CVS does (do a clone the first time, then to a pull  
> each time after that).

Correct.

> Three questions:
>
> 1) is the a particular label that I'd want to use.  I want current  
> stable, not latest dev

Can't quite do this in git.  When we package a release, we add a tag  
to git that indicates the exact state of the development tree at the  
time of packaging.  So, e.g., if you wanted to checkout the tree at  
the release of horde-4.0.9, you could go into the git tree and run the  
following command:

git checkout horde-4.0.9

However, since all of our applications now live in a single repo, it  
isn't possible to check them out separately.  So the above example may  
have imp in a state slightly before it was released (although  
generally applications are packaged/released at the same time, so the  
above should almost certainly represent the state of the other  
applications released at the same time as Horde 4.0.9).

To upgrade to the next release, you would have to manually do "git  
checkout horde-4.0.10" after it is released.  There is no "Stable  
Tracking Branch" since, as explained above, there is no single point  
in the git tree.

Currently, git master is essentially both the latest dev branch and  
also the branch used to create the new stable releases.  We currently  
have a 'develop' branch, but I'm not sure how much work has gone in  
there yet.

> 2) could I continue to use similar logic below, basically to  
> automate the pull for current stable?

Don't need to.  You can do a git pull at any time to update the repo.   
But your checkout won't change (if you are on a branch other than  
master) unless/until your explicitly request it.

> 3) will my config's be broken from going from FW_3 to current?

Yes.  Read docs/UPGRADING in the various applications for further information.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]