Bug Parade Engage 0.1 Update 38
obara.justin at gmail.com
Mon Oct 19 15:00:34 UTC 2009
Hello, I have spoken with James on the IRC channel and it seems that
we should be fixing http://issues.fluidproject.org/browse/ENGAGE-132
for 0.1 as well.
On 16-Oct-09, at 6:47 PM, Colin Clark wrote:
> We're in the home stretch now for freezing Engage 0.1. At this
> point, I think we just need confirmation on a few issues and then
> we're ready to go. I've added notes below with questions about the
> status of the remaining open issues.
> Needs review:
> EVERYTHING--let's schedule time for a group code review on Monday
> Engage 0.1 Bug Parade
> Code Clean up
> * Anything else left to clean up, or are we good?
> Create the directory structure for the Engage 0.1 release and move
> the relevant pieces from the incubator
> * Are we going to move Engage out of the incubator before or after
> we release? Other than that, the directory structure is all in place.
> Create Engage build scripts
> * This is looking pretty good. Any last tasks still to do?
> The fluid-all externals are named ambiguously and the Eclipse
> projects for engage-server and engage-client are incorrectly named
> * We renamed "engage" to "engage-core," but we still need to rename
> "infusion" and "kettle"
> Colin Clark
> Technical Lead, Fluid Project
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work
More information about the fluid-work