Sesat
>
Docs + Support
>
Upgrade Guides
>
Writing Upgrade Guide guidelines
Get Sesat
What is Sesat?
Download
Features
Screenshots
License
Documentation
Getting Started
Sesam.com tutorial
FAQ
...
more
Development
Roadmap
Subversion Repository
Mailing lists
Issues
Projects
Search Framework
Search Library
Mojo
User Service
Commons
Contextual IoC
Interpreter
Reflection
Reference Map
Visitor
Sitemap
Sitemap
Prefix page with {toc:indent=5}
The page should contain three h1. headings: Compatibility changes, New Features, and Requirements
Each "change" should be a h6. heading and include a date stamp
Each "change" should refer to a scarab issue
Each "compatibility change" has it's body text quoted
Each "compatibility change" should list separately: Changed API, Added APIs, Removed APIs, Deprecated APIs, and equivalents for SPIs.
© 2007-2009
Schibsted ASA
Contact
us