This does not appear correct: /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.6/bin$ ./cap --version Capistrano v2.5.0
On Tue, May 26, 2009 at 7:27 PM, Lee Hambley <[email protected]> wrote: > Hi All, > Firstly, I haven't released the 2.5.6 gem yet, the gemspec is ready to go, > and if this short round of open testing goes OK, I will release it as soon > as I receive some positive feedback. > It's been a while coming, and there have been lots of patches and > suggestions from a large number of people in the community. > In a bid to share a little knowledge, I want to let people know that about > midnight today, I tagged 2.5.6, which I *hope* is ready for a few people to > take a look at, give me a sanity check, and if all is well - we can roll > with it. > So, what's new... well here's a summary: > > deploy:migrate has gone, it's in an extension you load in the capfile now > start, stop and restart tasks have gone, they too are in an extension, some > of them, anyway... if you load the passenger extension, there is only a > restart task, for example > shared_children is undefined now, this is a railsism and has also been moved > to an extension. > > .. why has all this stuff gone? Well the migrations, and shared children, > everyone deploying Rails needs, but anyone using Sinatra, PHP, python or > similar.. ends up having to skip loading `deploy.rb` and not even getting > the versioned deploy code. Now, out of the box, a deploy will make a new > release directory, use your deploy:strategy to get the code into it and then > update the symlink. There is more in the CHANGELOG.rdoc > Loading the extensions should inject the tasks back into the flow where they > were, the only slight caveat might be the order in which the extensions are > loaded, but that is all defined in the new, longer and more verbose default > capfile, if you don't fancy re-capifying your app (and I wouldn't suggest > it) - then you can check out a copy in the readme here: > > http://github.com/capistrano/capistrano/tree/master > > There are more changes, some major, some minor, I've tried to lower the > barrier to entry, and I have more coming in the way of documentation > ( http://github.com/leehambley/capistrano-handbook ) - patches and issues in > the form of suggestions welcome, i have a pretty long list and will continue > to be working on that when I have the time; working on code and merging > patches has taken up all my time these last few days. > So, if you think you might like to try 2.5.6, there is more info in the > readme, how to install it and how to get a copy... I have summarised below: > > git clone git://github.com/capistrano/capistrano.git capistrano-capistrano > cd capistrano-capistrano > gem build capistrano.gemspec > sudo gem install ./capistrano-2.5.6.gem > > then to run your deploy against either 2.5.5, or 2.5.6 (or any other, of > course) try this: > > cap _2.5.5_ <task> > cap _2.5.5_ deploy > cap _2.5.6_ <task> > cap _2.5.6_ deploy:pending > > Feedback more than welcome, I am very aware that people might need a little > time to adjust to this, but by thinning out the magic, I hope that people > will be more able to get involved a little, especially given that Rails > isn't the de-facto ruby app now, and we are however a Ruby app community, > not a rails one! > - Lee Hambley > > > > -- Byron --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
