<p>Merb 1.0 will be available as a gem called merb-stack. This page is for planning what that will require:</p> <ul> <li>Merb Core</li> <li>Merb More <ul> <li>merb-action-args turned on by default</li> <li>merb-assets (cleaned up and documented) <ul> <li>the bundler must work</li> <li>we should add a JS and <span class="caps">CSS</span> minimizer</li> <li>we should figure out what the best bundling strategy is</li> <li>remove the view helper methods and move them to merb_helpers (merb-helpers?)</li> </ul></li> <li>should we move merb-builder out of merb-stack? <ul> <li>I think we can, if we do include merb-haml. haml makes building xml a breeze.</li> </ul></li> <li>merb-cache (benburkert is currently working on a rewrite) <ul> <li>we need to be very clear that our caching support meets all use cases</li> </ul></li> <li>merb-freezer will be built into merb-core as of 0.9.6</li> <li>merb-gen must be cleaned up and generate useful stubs, including testing tips</li> <li>merb-haml (I think this should be bundled with merb-stack, especially given how small it is)</li> <li>merb-jquery (at the very least, we need to add support for a Form Builder that automatically adds client-side validation to DM)</li> <li>merb-helpers needs to be merge in from merb-plugins <ul> <li>we need to decide what, other than the helpers, that we&#8217;re going to keep</li> </ul></li> <li>merb-mailer <ul> <li>are we going to try to get merb-notifier into 1.0 (antares)?</li> </ul></li> <li>merb-parts</li> <li>merb-unicode (big endeavor, maybe post-1.0)</li> <li>merb-slices <ul> <li>this needs to work, tests run, and very well documented. This is a crowning jewel of the merb stack</li> </ul></li> <li>dm-core</li> <li>dm-more</li> <li>extlib</li> </ul></li> </ul> 2008-09-05T18:53:54-07:00 53037 merb-stack 26 2008-09-06T12:35:46-07:00 2833