Roadmap

Roadmap

Fubu 1.0 Release

Right now, the thinking is that we'll make a public beta release at the end of April 2011 and the official 1.0 release around June 1, 2011.

In progress

1. New solution / new project / new package project “warmup” commands Sam Merrell
2. Fubu "Continuous Delivery" recipes based on "Bottles" (the packaging) ** Team Dovetail **
3. Spark cleanup ** Josh Arnold, Alex, Jaime **
4. Pull Packaging into the new "Bottles" project and repository
5. Release HtmlTags 1.0 ** In progress (Josh Flanagan) **
6. Mono CI build. Alex / Dale
7. Improved Diagnostics Package ** Josh Arnold **
8. Run FubuMVC via Mono XSP from a console app or embedded DLL. “Fubu in a box” ** Alex **
9. Add Xml comments to all public API’s ** Jeremy **

TODO

1. Review of all the Http abstractions
2. Split the repository 2. FubuCore & FubuLocalization 3. FubuFastPack 4. FubuMVC: FubuMVC.Core, spark integration, StructureMap integration 5. FubuValidation and FubuMVC.Validation package
3. Release FubuCore 1.0
4. Release Bottles 1.0
5. Rename the InvokePartial API to eliminate confusion with Partial(). InvokePartial code sucks, but it serves its purpose.
6. Remove Webforms support to a new project
7. Razor support -- pending the Spark cleanup work so we can reuse the pattern
8. Documentation!!!
9. Guides
   1. Model binding
   2. Url / Route conventions
   3. Url resolution
   4. Html conventions
   5. Action discovery
   6. Working with BehaviorGraph
   7. “Filters”
   8. Building custom Behaviors
   9. Bootstrapping and application
   10. Authorization
   11. Navigation
   12. IoC integration
   13. Building and using packages
   14. Localization
   15. Validation integration
   16. Html helpers
10. Flesh out default conventions for routes, html conventions, action selection. FubuRegistry on a new project should be as empty as possible
11. Script Manager improvements
    1. “PageScript” -- automatically push PageScript("name.js") to the bottom of the dep. graph
    2. Localization script. I.e., use scriptname.en-us.js or scriptname.en-gb.js
12. StoryTeller test coverage for all major features. StoryTeller CI build. Possibly switch to WebDriver / Selenium 2 to get browser matrix. Maybe start FubuMVC.StoryTeller for reusable test infrastructure.
13. Improve test coverage
14. Sample application(s). FubuMusicStore? FubuNerdDinner just doesn’t work very well
15. Revisit the "FubuContinuation / Redirectable" model. Maybe an "InterceptedActionCall"?
16. Eliminate all the TODO's in the codebase
17. Deal with any ignored tests. Eliminate them if they don't add any value
18. Add StoryTeller tests to the CI build.
19. Review all FubuRegistry public API's

Completed

• Dovetail team to convert “blue” codebase to FubuValidation
• Move Dovetail “crud” infrastructure to FubuFastPack
• Clean up BehaviorGraph / ObjectDef based on feedback from the FubuFastPack work
• Model binding work over. Remove all service location. Enable runtime selection of binders. Eliminate the Lambda model inside value converters. Driven by feedback from writing custom binders and converters in FubuFastPack
• Move script manager url from _scripts/_images to _content/scripts
• XSS and anti-forgery token
• Moved HtmlTags to a separate repository
• Simple Content negotiation support in ObjectResolver. Choose serialization or model binding dependent upon mimetype of request, default to model binding. Not trying to play a fullblown "FubuRest" card ** Jeremy **

Deferred

• FubuMVC.Validation package. Reusable validation integration “recipes.” Html conventions, BehaviorGraph conventions, pipeline integration. Should be possible to swap other validation engines in later
• IoC integration guidelines and acceptance tests
• Windsor integration

##Medium Term

1. Redo the Url/Route conventions (???)
2. Integrate fubu “Bottles” support with either Nuget or OpenWrap
   1. Package dependencies
   2. Package ordering
3. Razor view engine integration
4. AutoFac integration
5. Advanced ScriptManager
   1. CoffeeScript integration
   2. LESS integration
   3. CSS/Script compression recipes
   4. Cdn.google.com (and analogues) integration

##Long Term

1. Html conventions everywhere
2. OWIN or OpenHttp support.
3. Eliminate all coupling to ASP.Net / IIS. Make IIS run in an adapter model to OWIN / OpenHttp.
4. NDjango view engine?
5. Other IoC containers?
6. NHaml support?