summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorShawn O. Pearce <sop@google.com>2009-02-18 14:42:27 -0800
committerShawn O. Pearce <sop@google.com>2009-02-18 14:42:27 -0800
commit68d126e1cea423c4e9f3678c227fdb1348d48cae (patch)
treef5b9963989783b99d11286b6ae38b04fed494a54
parent2335b6dd60b6b034344667bccfbb4a2df46495e6 (diff)
Remove old entries from our feature roadmap
These have either been met, or are rather moot to talk about. Signed-off-by: Shawn O. Pearce <sop@google.com>
-rw-r--r--Documentation/feature-roadmap.txt24
1 files changed, 0 insertions, 24 deletions
diff --git a/Documentation/feature-roadmap.txt b/Documentation/feature-roadmap.txt
index 4e806122a6..dc34d5c7ed 100644
--- a/Documentation/feature-roadmap.txt
+++ b/Documentation/feature-roadmap.txt
@@ -1,11 +1,6 @@
Gerrit2 Feature Roadmap
=======================
-Everything Gerrit1 does
------------------------
-
-This list is long so I'm not listing it all here.
-
Offline Support
---------------
@@ -24,22 +19,3 @@ allow corporate contributors to open source projects to use a
Gerrit 2 server internally to review (and scrub protected IP)
prior to submitting changes upstream to a public Gerrit server
and an established open source project.
-
-No Google Requirement
----------------------
-
-Gerrit 2 must not require any Google services to run. This makes
-it suitable for installation inside of corporate firewalls where
-information security demands certain data stays internal.
-
-Arbitrary SQL Database
-----------------------
-
-Gerrit 2 should support any standard SQL database, including
-popular open source (PostgreSQL, MySQL, SQLite) and pure Java
-implementations (H2). Some commerical servers may wind up being
-supported, but only by virtue of Gerrit 2 sticking to a very small,
-commonly implemented subset of SQL.
-
-This requirement (and the prior one) means Gerrit 2 won't run on
-Google App Engine, as GAE does not support arbitrary SQL syntax.