Builder bug parade update

Colin Clark colinbdclark at
Fri Jan 8 22:57:38 UTC 2010

Hi all,

A quick update on the status of the Infusion Builder. We hit another  
blocker during QA testing, documented here:

It's a somewhat elusive issue but severe enough that we don't think  
the Builder is quite ready for release at this point. The fix is  
foundational, involving a change to the way we process and respond to  
requests in the server-side PHP code.

As a community, we're juggling a lot right now. I'd like to simplify  
the development roadmap a little bit by putting the Builder on the  
shelf for a few months while we focus on producing the next release of  
Engage. We have a key milestone in mid-February with McCord's pilot of  
Engage in their museum, which we're all really excited about. Once  
Engage 0.3 is out, we'll dive back into the last major blocker for the  
Builder and aim to get it out in the spring.

I know this is all a little disappointing for everyone, and I'd like  
to thank you all for your hard work designing, developing, and testing  
the Builder. It'll come.


On 5-Jan-10, at 6:51 PM, Colin Clark wrote:

> Hi all,
> As Justin mentioned before the holidays, a few unexpected issues  
> popped up during QA testing for the Infusion Builder. We've reopened  
> the bug parade and the problems have nearly all been addressed.
> It looks like the last outstanding tasks involve getting the new  
> deployment server all set up for the Builder, and doing final code  
> review on the changes to the Infusion Ant build scripts. We hope to  
> wrap this work up tomorrow.
> This release of the Infusion Builder will ship with three primary  
> known issues:
> * Users can't exclude modules that are required by another selected  
> module (even if they're unchecked)
> * If an unexpected error occurs, the Builder reports errors in a way  
> that isn't particularly user-friendly
> * Clicking the download button causes an abrupt page transition and  
> shows an activity indicator that spins infinitely, even after the  
> download has begun.
> The plan is to free the code again and start QA testing tomorrow. We  
> really, really need help with testing (it's not hard), so if you've  
> got some spare cycles this week and can lend a hand, please let the  
> list know.
> Colin

Colin Clark
Technical Lead, Fluid Project

More information about the fluid-work mailing list