Jamis: Thanks you very much for the update.
On Mar 15, 2:51 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > Capistrano edge works great...but it has no deployment support. I > should have the capistrano-deploy package ready in a week or two, if > all goes well. I've been working like mad on Highrise > (http://www.highrisehq.com), and I'll be at the MountainWest RubyConf this > weekend...and then I still need to get my RailsConf presentations > ready...but I'm making time for Capistrano. I can't thank you enough for the hard work you put in to Capistrano. I been late to rails party so capistrano was really cool now that I am planning to release my site. > Note, though, that 2.0 won't be 100% backwards compatible with your > existing 1.x deployment recipes. And, currently, there's no way to > have both 1.x and 2.0 installed at the same time, which means that > you have to upgrade wholesale if you want to upgrade at all. I'm > still working on ways to make the upgrade path smoother. Not a problem for me :-) Late to the party yes but others have paved the way :-) > In general, cap2 is MUCH better tested (close to 100% C0 code > coverage, though I know that can be a misleading metric), and much > cleaner. There is no more Capistrano::Actor-- > Capistrano::Configuration now does all of what Actor used to do. I'm > really, really excited about it...but I don't feel like I can release > it until I can provide a way to upgrade existing recipes cleanly. I completely agree with you but I also think its not a bad idea to do a release for the folks that has no "previous versions" "starting fresh". I hope you will consider some sort of pre-release. Even though I can get things out of trunk but it will be nice to have a "ok stable" version that doesn't change a lot. I also understand what it means to release so this is just my wish :-) > Please do feel free to experiment with edge and if anyone has any > success in running both cap versions side-by-side, I'd love to hear > from you. Will do. Thanks again for the update. > > > Hi Jamis: > > > Can I back to edge now or is it still a bad idea? I am specifically > > wondering > > about the SCM module i.e local subversion repo > > >http://blog.wolfman.com/articles/2006/12/06/a-capistrano-scm-module- > > for-local-svn-access#comments > > > Thanks for any update. > > > Cheers > > > On Feb 26, 2:28 am, Jamis Buck <[EMAIL PROTECTED]> wrote: > >> Just a word to the wise: if any of you are tracking Capistrano edge > >> (and I have no idea how many people actually are), things are going > >> to get pretty wild, shortly. I'm going to begin some massive > >> refactorings, leading eventually to Capistrano 2.0, and I can > >> guarantee that for the next little while Capistrano on edge will be > >> virtually unusable (and will probably not even run). > > >> If you are tracking edge, I'd encourage you to track the stable > >> branch, instead: > > >> http://svn.rubyonrails.org/rails/branches/capistrano_1-x-stable > > >> So, you have been warned! Edge is going to become extremely volatile > >> and experimental, and you may very well see stuff that makes no sense > >> getting committed. Feel free to send email to this list commenting on > >> recent commits, if you feel so inclined. > > >> Onward! > > >> - Jamis > > >> smime.p7s > >> 3KDownload --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
