Bug Parade Engage 0.1 Update 38

[michelle.dsouza at utoronto.ca]

This is great news! I put some comments about ENGAGE-95 below.

Michelle

Quoting Colin Clark <colinbdclark at gmail.com>:

> 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
> ===================
>
> General:
>
> Blocker
>
> FLUID-3208
> Code Clean up
> http://issues.fluidproject.org/browse/FLUID-3208
>  * Anything else left to clean up, or are we good?
>
> ENGAGE-88
> Create the directory structure for the Engage 0.1 release and move the
> relevant pieces from the incubator
> http://issues.fluidproject.org/browse/ENGAGE-88
>  * 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.
>
>
> ENGAGE-95
> Create Engage build scripts
> http://issues.fluidproject.org/browse/ENGAGE-95
>  * This is looking pretty good. Any last tasks still to do?

If we do the remaining tasks in ENGAGE-70 we will need to tweak the  
build. Other then that there is one clean up task for the build which  
has to do with removing the repetition between the Infusion build  
scripts and Engage build scripts. It's FLUID-3243 and should probably  
be left until after the release.

>
>
> Major
>
> ENGAGE-70
> The fluid-all externals are named ambiguously and the Eclipse projects
> for engage-server and engage-client are incorrectly named
> http://issues.fluidproject.org/browse/ENGAGE-70
>  * We renamed "engage" to "engage-core," but we still need to rename
> "infusion" and "kettle"
>
> ---
> Colin Clark
> Technical Lead, Fluid Project
> http://fluidproject.org
>
> _______________________________________________________
> fluid-work mailing list - fluid-work at fluidproject.org
> To unsubscribe, change settings or access archives,
> see http://fluidproject.org/mailman/listinfo/fluid-work