From Lift

Ask yourself what needs to be done before lift is "1.0" worthy." If lift 1.0 was released during JavaOne 2008 (May 06), what would it need to ensure success?

Contents 1 Left to do 1.1 Documentation 1.2 Features 1.3 Process 1.4 Community 1.5 Marketing 2 Completed 2.1 Documentation 2.2 Features 2.3 Process 2.4 Community 2.5 Marketing

Left to do

Put your best 1.0 ideas here and help the project succeed.

Documentation

• API documentation
• Getting Started
• AJAX & Comet guide
• REST Guide
• Screen casts
• Building a whole application
• Book (maybe)

Features

• Test infrastructure
• Unified Validation framework
• Widget Framework (how to create/package, to use, to customize/compose)
• a testkit : test framework/helper for lift's users
• Database partitioning... read from slaves write to master

Process

• Release process
• Tests
• Packaging
• Hosting for API docs, etc.

• Clean up codebase for 1.0 including removal of legacy and/or abandoned features.

Community

• Listing of lift-powered applications
• lift consultancy?

Marketing

• Official Logo
• Wiki Graphic

Completed

Documentation

Features

• I18n
  • Templates
  • Word lookup table
• RabbitMQ integration
• New Project Builder
• Finish SiteMap
• Improve statefulness of snippets (See Daniel Green's widget system proposal)
• JSON rendering and diffing for Comet
• XMPP support
• Better Error Handling/Display Control (ability to specify error pages/etc so that end user does not see an exception)

Process

Community

Marketing