On Mon, Nov 11, 2013 at 7:53 AM, Joshua Harlow wrote:
> I can put an upper bound on the version, that's fine with me. I'd rather
> not avoid adding taskflow to wait until some new preemptive gating process
> is in place. That doesn't exactly feel fair to the people creating taskflow
> or the peopl
Sweet, let me know if u have any questions, bug me when I get back
tomorrow (spent some time in HK to travel around, since during the summit
most all the traveling was from the airport to the asiaworld) making it
hard to actually see any of hong kong (except at night). So let me know if
u want to d
Yes it's still a thing and no it's not being deprecated, I heard other things
from other people at rackspace say the opposite, so maybe u misunderstood
adrian (if or if not rackspace is involved is there choice in the end).
So yes it's still being actively developed and yes it's gaining tractio
Feel free to read over this too:
http://www.slideshare.net/harlowja/taskflow-27820295
I'm not sure where the video I did at the summit is (still being uploaded??)
but that's the slides that I went through in my speaker session.
Questions and comments welcome.
Sent from my really tiny device...
On 12 November 2013 22:47, Joshua Harlow wrote:
> Yes it's still a thing and no it's not being deprecated, I heard other things
> from other people at rackspace say the opposite, so maybe u misunderstood
> adrian (if or if not rackspace is involved is there choice in the end).
>
> So yes it's s
So I'm curious - is taskflow still a thing? Adrian was saying in HK
that Rackspace wasn't investing in it any more as another library -
Spiffy? - was functionally superior, and there is no need to reinvent
the wheel.
If thats the case, should Mistral be built on Spiffy, and taskflow deprecated?
-
Sounds good,
Will do when I get back from HK, still here exploring :-)
Sent from my really tiny device...
> On Nov 11, 2013, at 10:17 PM, "Monty Taylor" wrote:
>
> Ok. Cool. Let's just put an upper bound on it for now then (mainly
> because it's listed as 0.1, so that version to me suggests th
I can put an upper bound on the version, that's fine with me. I'd rather not
avoid adding taskflow to wait until some new preemptive gating process is in
place. That doesn't exactly feel fair to the people creating taskflow or the
people using it, especially since people are integrating it at th
Ok. Cool. Let's just put an upper bound on it for now then (mainly
because it's listed as 0.1, so that version to me suggests that it might
still have breaking API churn)
On 11/11/2013 07:53 AM, Joshua Harlow wrote:
> I can put an upper bound on the version, that's fine with me. I'd rather not
>
Monty Taylor wrote:
> There is a change up to add taskflow to the global requirements. I have
> no problem with this in principle, but it's one more that's in the set
> of things like pecan, wsme and friends that are in the set of things
> that Sean talked about in preemptively gate the universe.
>
There is a change up to add taskflow to the global requirements. I have
no problem with this in principle, but it's one more that's in the set
of things like pecan, wsme and friends that are in the set of things
that Sean talked about in preemptively gate the universe.
I'd like to not add it until
11 matches
Mail list logo
