roadmap.txt

# Rails 3.1

- Yehuda's Windy City Talk: http://dl.dropbox.com/u/2285145/Rails%203.pdf

## RSoC Merges

- Identity Map (ET)
- Code Reloading (JK)
- Benchmarking CI (YK)
✓ Engines++ (JV)

## Assets

✓ Rack::Static (JV)
✓ Rack::Cache (YK)
- Assets compiler pipeline (YK, CL, in progress)
- //= require compilation
- Stylesheets compiler (YK, CE)
  ✓ Builtin: Compass Spriting (pure-ruby) (working in Compass)
  - Builtin: SCSS/Compass (in progress, Chris Eppstein)
  - Write plugin for: Less
- JavaScript compilation
  - Builtin: ERB
  - Write plugin for: CoffeeScript

## Extras

- Rails Parts (JV) -> nixed until 3.2
- Exceptron (JV)
- Flush (YK/JV/JK)
  - Fiber/Thread-based flow control

## Deprecations (Rails Core Team)

✓ Remove 3.0 deprecation warnings
- Add 3.1 deprecation warnings
  - AR
  - AM
  - Router
  - RJS
  - Template Handler API

## Performance

- Aaron's Arel rewrite (AP)
- More aggressive work on ActionPack (YK)
- Aim for 2x over Rails 3.0

## Ship it

Is there an overview on the changes for Engines? I'll need to create a clear upgrade path for the 200+ Redmine plugins.

Did you take a look at the slides? There's a lot more in there.

edavis10: Here's a write-up from the author http://piotrsarnacki.com/2010/09/14/mountable-engines/

jlindley:

Thanks. It looks like Rails3 Engines are going to be a problem because of the changes in db migrations. Hopefully the old way will still work since it's better for applications that have their own plugins (e.g. Redmine).