Hey, As a blocker for 1.3, I think we'll want some documentation that specifically lists each function in the framework that is being released in sneak peek form. I don't think we need to, for example, get all of the IoC system documented in time for the release, but we will want it to be very clear which portions of the framework are subject to change in 1.4 and 1.5.
King, here's my petition: can we file a JIRA for this task and make it a blocker for this release? Most of the others below could maybe be marked as critical? Colin On 2010-10-04, at 2:16 PM, Cheetham, Anastasia wrote: > > Justin, there are a number of new "sneak peek" framework features that we > really should make sure are documented before we release. Can we get some of > these JIRAs into the bug parade, just to make sure we don't release without > them? > > FLUID-3716 > Document the IoC API > http://issues.fluidproject.org/browse/FLUID-3716 > > FLUID-3717 > Update Framework API docs to reflect additions, bug fixes > http://issues.fluidproject.org/browse/FLUID-3717 > > FLUID-3719 > Update Renderer docs to reflect updates, bug fixes > http://issues.fluidproject.org/browse/FLUID-3719 > > FLUID-3773 > Document changes to the ChageApplier/Data Binding > http://issues.fluidproject.org/browse/FLUID-3773 > > And if there are other new features/changes that I should add to the list, > please let me know! > > -- > Anastasia Cheetham Inclusive Design Research Centre > [email protected] Inclusive Design Institute > OCAD University > > _______________________________________________________ > fluid-work mailing list - [email protected] > To unsubscribe, change settings or access archives, > see http://fluidproject.org/mailman/listinfo/fluid-work --- 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
