No problem and thanks for that info Lee. I'll update and use the capistrano-maintenance gem. Thanks again. -md
On Friday, November 9, 2012 12:25:48 PM UTC-5, Lee Hambley wrote: > > I believe it was a release oversight, please see > https://github.com/capistrano/capistrano/commit/4ece7902d5 > <https://github.com/capistrano/capistrano/commit/4ece7902d5> or > more information. (I believe that conversation thread would be better > continued in an Issue) The last few releases have been done by a new member > of the maintenance team, and I believe there were a few spanners in the > works. I haven't been personally involved in the release cycle for a while. > > I can't give a lot more information, other than to apologize for the > inconvenience, and direct you there. > > Regards, Lee > > On 9 November 2012 18:12, Michael DelGrosso <[email protected]<javascript:> > > wrote: > >> I was surprised to see the deploy:web:disable, and deploy:web:enable >> tasks removed in v2.13.5. Did I miss a deprecation notice? Have they been >> replaced with an alternative? Is/was it bad practice to be using these >> tasks? Just curious as I had used them often. >> >> -- >> * You received this message because you are subscribed to the Google >> Groups "Capistrano" group. >> * To post to this group, send email to [email protected]<javascript:> >> * To unsubscribe from this group, send email to >> [email protected] <javascript:> For more options, visit >> this group at http://groups.google.com/group/capistrano?hl=en > > > -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
