cleanup run by default in v3

[James Almond]

Hi,

We've recently upgraded an old app to v3. From what I can see v3 now automatically cleans up on deploy with 5 releases set by default. Searching through the issues, in the past the position has generally been "we'll never delete production code by default" [1] (which I'd generally agree with) and it had to be configured. I was wondering whether running cleanup be default was now the expected behaviour or a bug/oversight?

Thanks,

James

[1] https://github.com/capistrano/capistrano/issues/89#issuecomment-29578116

----

http://jamesalmond.com

[Lee Hambley]

I dare say oversight, but we get many more people annoyed by "server disk space exhausted" than "you cleaned up obsolete releases". I think I may have caved to the heavier weight argument at some point, but probably I shouldn't.

Code seems to have been introduced here https://github.com/capistrano/capistrano/commit/ebd8fee20ad3b3d2930efdba8044e4e578be4078 - however now that it's in, it's always tricky to reverse behaviour without annoying people, or catching them out.

I'm conflicted, but please feel free to open an issue to restore/fix/correctly documetn (as you see fit) and I'll pull in some of the other frequent contributors to offer their opinions.

Lee Hambley

http://lee.hambley.name/

+49 (0) 170 298 5667

--
You received this message because you are subscribed to the Google Groups "Capistrano" group.
To unsubscribe from this group and stop receiving emails from it, send an email to capistrano+...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/capistrano/f3f9507d-a9ce-4600-b088-8c8434731c95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.