Re: [Fab-user] Beta 1 out

[Niklas Lindström]

Hi Jeff,

nice progress! I just ran it and have some sketchy remarks (a bit
short on time, so do request for more details if this is a blur):

1. It seems the old issue I had with a command failing to return
("tomcat start") is in 0.9b1 but not on master (provided "git-checkout
0.9b1" switches to that and "git-checkout master" switches back, which
is how I tested this).

2. I cannot use --roles=<roles> or -R<roles>, but
<command>:roles=<roles> and @roles works..

3. I have to decorate commands with @roles even if they only call
other commands that are already decorated with @roles. Is this
intentional/hard to fix? (I haven't dabbled much with roledefs etc
before). Example::

    @roles('main')
    def deploy_main(): ...

    @roles('main') # <-- should I need this?
    def main_all():
        package_main()
        deploy_main()


4. A thing which worked in the old fabric 0.1, was to call another
function which sets ``env.hosts`` (actually, I think it only worked
via @depends). Thus, with::

    def setup_a():
        env.hosts = ['localhost']
    def ls_a():
        setup_a(); run("ls")

, when I do "fab ls_a", Fabric prompts me for host. (I really don't
need this right now when I use roles though..)

5.  `fabric.contrib.files.exists` fails intermittently (on an ubuntu
server). I get the feeling it fails to capture the result "in time" or
something.. Instead, I use ::

        exists = lambda path: not run("test -d %s" % path).failed


That's all for now.

Best regards,
Niklas



On Fri, Jul 3, 2009 at 7:02 AM, Jeff Forcier<address@hidden> wrote:
> Hi all,
>
> Fabric is now officially in beta!
>
> This means a feature freeze; I'd like for there to be zero behavioral
> changes, with only bugfixes and docs/test updates between now and
> final. If something critical comes up I may sneak in a change or two,
> but I'd prefer everything possible to be pushed off to 1.0.
>
> To facilitate this, I have branched Fabric: there is an 0.9 branch for
> the beta, then final and post-final releases, and master is now what
> will become 1.0, with the expected new features and accompanying
> chance of bugs. The docs now reflect this, having per-branch
> subdirectories (vague requests get redirected to the stable version.)
> There's a note at the top of every page making this obvious, the idea
> being stolen directly from docs.djangoproject.com. This may not be the
> last good idea I borrow from them :)
>
> Finally, the only behavioral difference between branches right now is
> that master has a new "reboot" operation (was in side branch, now
> merged/deleted.) Feel free to give me feedback on the current
> implementation, it's rough but works-for-me in the one use case I
> wrote it for.
>
> Please let me know if I've goofed anything up with this reorganization
> and I'll fix it post-haste. Otherwise, I plan to focus on fixing bugs,
> building up the test suite and overhauling the docs so we can get 0.9
> final out the door.
>
> Thanks as always,
> Jeff
>
>
> _______________________________________________
> Fab-user mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/fab-user
>