Bug Parade Engage 0.1 Update 38
michelle.dsouza at utoronto.ca
Mon Oct 19 16:09:33 UTC 2009
I feel like we should leave a couple of these for the next release.
What we are building right now is reasonable for an 0.1 release
especially given the loading page that Justin and Jacob are working
on. I've got more comments inline below.
On 16-Oct-09, at 6:47 PM, Colin Clark wrote:
> Code Clean up
> * Anything else left to clean up, or are we good?
We are going to do the code review today. If anything small comes up
we'll fix it with this JIRA and then resolve it.
> 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.
I think we should wait until after the release. This means that part
of the incubator will be subject to code freeze but given that it was
already subject to bug parade rules it doesn't seem like too big a
stretch. We can do this first thing when the repository opens up again.
> Create Engage build scripts
> * This is looking pretty good. Any last tasks still to do?
I resolved this issue and commented on ENGAGE-70 that the build
scripts will need to be updated.
> 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"
All three need to change to have 'fluid' in front of them and the
eclipse projects will need to change also. Again, I feel like we
should wait until the repository opens up again.
Software Developer, Fluid Project
Adaptive Technology Resource Centre
University of Toronto
More information about the fluid-work