On Sun, Feb 26, 2012 at 7:33 PM, Jeff Forcier <[email protected]> wrote:

> ## Fabric 2
>
> [...] A backwards incompatible release is an inevitability.
>
> [...] We may rewrite moderate chunks [...]

Clarification: there will not be (m)any enormous/disruptive changes --
the same use cases will work, just with modified/improved APIs. We'll
also include transitional methods when it's easy to do so.

For example, we'll move from host strings to host objects (eliminating
internal cruft) and split "env" into multiple objects/namespaces (less
confusion, user errors and bugs.)

But we'll ensure the "quick script / no boilerplate" use case still
works, by (for example) preserving a "user@host:port" host-creation
shortcut.

End result should be a much improved infrastructure (+ a better
library-use story) without turning into something totally alien.


Thanks,
Jeff


-- 
Jeff Forcier
Unix sysadmin; Python/Ruby engineer
http://bitprophet.org

_______________________________________________
Fab-user mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/fab-user

Reply via email to