Hey all, Our goal is to freeze the Engage 0.3b code base this afternoon, with the exception of performance optimizations. A bunch of developers had a quick status update in the IRC channel. Here are the details:
On 2010-02-18, at 9:53 AM, Jess Mitchell wrote: > ----------------------------------------------------------------------------- > TO FIX (remaining bugs): > BLOCKERS: > 342: Performance of 0.3 is slow even when hitting from an iPhone on wifi > 402: Prune unnecessary JavaScript and CSS dependencies from the application These two are on my plate for today, and I've already started on ENGAGE-402. The ENGAGE-342 is actually just an umbrella issue, so I think we should remove it from the parade and replace it with ENGAGE-349: Concatentate and Minify. I've taken the liberty of going ahead and doing this. :) > 357: Implement a component allowing users to view and edit comments and notes > on Artifacts and Exhibitions We're waiting on the status of this from Antranig, but judging from commit logs, we're getting close. > 356: Message Bundles are not being located for the standalone (war file) > version, for services using spouts This appears to have been committed and is working in the daily build. Can it be closed, Antranig? > 307: Implement the "Save and send my collection to me button" in My Collection Sveto is taking point on this, and will hand it off to Yura when he's finished for the day. Yura will finish it up and submit a patch for review. > 348: Ensure that My Collection is internationalizable My Collection is fully internationalizable now, so I've gone ahead and closed this one. We do have a few outstanding strings to translate, so I've created this ticket and filed it as a blocker for the bug parade: http://issues.fluidproject.org/browse/ENGAGE-403 > Critical: > 395: The Collect/Uncollect button and associated status message aren't > styled correct in Artifact View Yura's finishing this one up and will submit a final patch today. > 324: Panel heading on Exhibitions Browse should read "Upcoming" and not > "upcomingCategory" This should have been fixed as part of ENGAGE-356. Antranig? > 331: On tap, tappables should highlight to indicate "touched" feedback Justin will commit a fix for this one shortly. > 380: Buttons are being read as "Button" This one is also on Justin's plate. > ----------------------------------------------------------------------------- > > TO COMMIT (patched but not in SVN): > 329, 389, 390 Justin's got these ones, too, with help from me as needed. Colin --- Colin Clark Technical Lead, Fluid Project http://fluidproject.org _______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
