On Sat, Jul 30, 2011 at 3:54 AM, Drew <[email protected]> wrote: > This is what I usually do. I have a branch called my_config that I > have pushed my changes in there. Now every now and then I do a git > pull and get the latest from git://gitorious.org/gitorious/mainline.git. > Some times gitorious comes up with no complains and some times I have > to either install new gems or run "rake db:migrate" >
The bundle install or rake migrate steps are two of the reasons why we went for versioning Gitorious. A patch version should not require: - rake db:migrate - bundle install Minor versions could require you to do so. So a rule of thumb would be to upgrade patch versions simply by using git pull, upgrading to a new minor version you should always both migrate and install gems, since that may be required. > But I did a "git pull" and that downloaded bunch of changes (which > broke gitorious, but I fixed it by installing new gems) > I ran "bundle exec rake changelog" again, but the output is the same. > If you did a git pull while on the master branch, that will have been updated. Our versioning scheme is based on using git tags to check out a specific version. > So my question is, how does "bundle exec rake changelog" work? If the > version hasn't changed, then what were all those changes that were > downloaded? > It will compare the available tags on the server to the current tag you're running with. Cheers, - Marius -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected]
