Skip to content
namelessjon edited this page Sep 12, 2010 · 6 revisions

Merb 1.0 will be available as a gem called merb-stack. This page is for planning what that will require:

  • Merb Core
  • Merb More
    • merb-action-args turned on by default
    • merb-assets (cleaned up and documented)
      • the bundler must work
      • we should add a JS and CSS minimizer
      • we should figure out what the best bundling strategy is
      • remove the view helper methods and move them to merb_helpers (merb-helpers?)
    • should we move merb-builder out of merb-stack?
      • I think we can, if we do include merb-haml. haml makes building xml a breeze.
    • merb-cache (benburkert is currently working on a rewrite)
      • we need to be very clear that our caching support meets all use cases
    • merb-freezer will be built into merb-core as of 0.9.6
    • merb-gen must be cleaned up and generate useful stubs, including testing tips
    • merb-haml (I think this should be bundled with merb-stack, especially given how small it is)
    • merb-jquery (at the very least, we need to add support for a Form Builder that automatically adds client-side validation to DM)
    • merb-helpers needs to be merge in from merb-plugins
      • we need to decide what, other than the helpers, that we’re going to keep
    • merb-mailer
      • are we going to try to get merb-notifier into 1.0 (antares)?
    • merb-parts
    • merb-unicode (big endeavor, maybe post-1.0)
    • merb-slices
      • this needs to work, tests run, and very well documented. This is a crowning jewel of the merb stack
    • dm-core
    • dm-more
    • extlib
Clone this wiki locally