Post Infusion 1.5 proposal

[Justin Obara]

That page is probably currently up-to-date, and is probably where we should start from. There are also comments in the code about parts being deprecated, but I'd assume they are all captured on this page as well. 

That being said, there are parts on this page that can't be removed just yet, as there needs to be work done to replace them. Also, we'll likely come across other parts of the code that we'll want to drop as we make changes in the code base, so this list wasn't expected to be exhaustive.

Thanks
Justin


On Jun 18, 2014, at 9:56 AM, Cheetham, Anastasia <acheetham at ocadu.ca> wrote:

> 
> On 2014-06-17, at 12:48 PM, Justin Obara wrote:
> 
>> Proposal 2:
>> 
>> After every release there is a lot of jira cleanup needed. I'd like to take the opportunity to close ("won't fix") all issues related to deprecated features, apis, and etc., as well as those that are specific to browsers we are no longer tracking.
> 
> This makes sense to me, in principle. Do we have a definitive list of what features, apis, etc. we'll be deprecating or removing for 2.0? I see this page:
> 
> http://wiki.fluidproject.org/display/fluid/Deprecations+in+1.5
> 
> Is it up-to-date? Complete? Who makes that final call?
> 
> -- 
> Anastasia Cheetham     Inclusive Design Research Centre
> acheetham at ocadu.ca           Inclusive Design Institute
>                                        OCAD University
> 
> <winmail.dat>