AMO: Difference between revisions

644 bytes removed ,  15 February 2005
no edit summary
No edit summary
Line 48: Line 48:


== Roadmap ==
== Roadmap ==
=== Getting to version 1.0 ===
=== v1.0 ===
Getting to v1.0 is all about plugging the holes and getting the service re-enabled.  We have some short timelines ahead of us that we need to take into account.  See the complete [[Update:Development:v1.0|v1.0 plan]].
 
=== Getting to version 2.0 ===
In our discussions on #umo we have talked about a few things in regards to v2.0.  The overall opinion is that we should rewrite completely from scratch so as to take advantage of frameworks/tools to scale the application and grow it over time better.  See below for a summary of questions regarding UMO v2.0.  See the complete [[Update:Development:v2.0|v2.0 plan]].
 
== v1.0 ==
We are only going to be doing security and performance fixes to this release.  This will tie into the [[Update:Development:v1.0|security audit]] which will identify any changes that need to happen before we turn UMO on with the v1.0 codebase.
We are only going to be doing security and performance fixes to this release.  This will tie into the [[Update:Development:v1.0|security audit]] which will identify any changes that need to happen before we turn UMO on with the v1.0 codebase.


Line 65: Line 59:
* [[Update:Infrastructure|Deploying UMO : Infrastructure]]
* [[Update:Infrastructure|Deploying UMO : Infrastructure]]


== v2.0 ==
=== v2.0 ===
The overall opinion is we should rewrite from scratch to take advantage of frameworks/tools to improve scalability and extensibility.  See the complete [[Update:Development:v2.0|v2.0 plan]].
The overall opinion is we should rewrite from scratch to take advantage of frameworks/tools to improve scalability and extensibility.  See the complete [[Update:Development:v2.0|v2.0 plan]].


3,035

edits