RedmineVersion » History » Version 3
Version 2 (Chris Cannam, 2010-09-17 11:37 AM) → Version 3/9 (Chris Cannam, 2010-11-19 01:09 PM)
h1. Which version of Redmine?
Our Redmine installation is made from a version maintained in an Hg repository (see "the Repository tab for this project":https://code.soundsoftware.ac.uk/projects/soundsoftware-site/repository).
This currently has two branches: @default@ and @yuya@.
The @default@ branch tracks Redmine trunk (we carry out an actual SVN checkout on top of the repo and commit the entire .svn tree).
The @yuya@ branch contains the Redmine Mercurial overhaul patches from Yuya Nishihara described at "Redmine issue 4455":http://www.redmine.org/issues/4455. This branch is the one that is actually used in the "production" site, and we merge to it from default each time we update default from trunk.
The aim is to track the Redmine trunk until Yuya's Mercurial overhaul patches are merged into trunk, and then to stop tracking the trunk at the next subsequent stable release.
h2. How to update to Redmine trunk
Example: I start out doing some work in my test server, on the @cannam@ branch. I have no uncommitted changes. I want to update the version of Redmine that my branch is based on.
First, switch to the @default@ branch. This (shared) branch is used only to track Redmine trunk.
@$ hg update default@
We have
Our Redmine installation is made from a version maintained in an Hg repository (see "the Repository tab for this project":https://code.soundsoftware.ac.uk/projects/soundsoftware-site/repository).
This currently has two branches: @default@ and @yuya@.
The @default@ branch tracks Redmine trunk (we carry out an actual SVN checkout on top of the repo and commit the entire .svn tree).
The @yuya@ branch contains the Redmine Mercurial overhaul patches from Yuya Nishihara described at "Redmine issue 4455":http://www.redmine.org/issues/4455. This branch is the one that is actually used in the "production" site, and we merge to it from default each time we update default from trunk.
The aim is to track the Redmine trunk until Yuya's Mercurial overhaul patches are merged into trunk, and then to stop tracking the trunk at the next subsequent stable release.
h2. How to update to Redmine trunk
Example: I start out doing some work in my test server, on the @cannam@ branch. I have no uncommitted changes. I want to update the version of Redmine that my branch is based on.
First, switch to the @default@ branch. This (shared) branch is used only to track Redmine trunk.
@$ hg update default@
We have