[maemo-commits] [maemo-commits] r16600 - projects/haf/doc/mvo

From: subversion at stage.maemo.org subversion at stage.maemo.org
Date: Thu Nov 6 17:12:06 EET 2008
Author: marivoll
Date: 2008-11-06 17:12:06 +0200 (Thu, 06 Nov 2008)
New Revision: 16600

Modified:
   projects/haf/doc/mvo/system-model-2.txt
Log:


Modified: projects/haf/doc/mvo/system-model-2.txt
===================================================================
--- projects/haf/doc/mvo/system-model-2.txt	2008-11-06 14:45:58 UTC (rev 16599)
+++ projects/haf/doc/mvo/system-model-2.txt	2008-11-06 15:12:06 UTC (rev 16600)
@@ -13,14 +13,14 @@
   components; how the Maemo system is bootstrapped from source; how we
   import upstream sources; how we handle NMUs; etc.
 
-  This text has been written before with Part I, so I had to make a
-  few assumptions about Part I that might turn out to be wrong.  The
+  This text has been written before Part I, so I had to make a few
+  assumptions about Part I that might turn out to be wrong.  The
   assumptions are:
 
   - We are talking about the "Maemo" system, from its Harmattan
     version onwards.
 
-  - Maemo contains a operating system (the "Maemo OS") that runs in a
+  - Maemo contains an operating system (the "Maemo OS") that runs in a
     variety of configurations on a variety of devices.  The OS
     includes programs, libraries, kernels, firmware, etc.
 
@@ -71,6 +71,22 @@
   - Upload and download rights are more complicated since
     unfortunately not everyone is equal in the land of Maemo.
 
+  There are differences to our current way of working as well, of
+  course:
+
+  - Everything is public by default.  There some support for keeping
+    things secret, but this should always be regarded as an exception
+    rather than the rule.
+
+  - The "extras" repositories are an inherent part of the plan.
+
+  - Everything is compiled in "testing" and released to "stable" from
+    there.  That includes 3rd party application developers.  "Testing"
+    must be good enough as an SDK for "stable".
+
+  - Upgrade chaining is not implemented by the archive.  We need to
+    come up with another way of doing it.
+
 ]
 
 * The Maemo archive
@@ -310,11 +326,11 @@
 The Maemo archive can and should contain the distributions for
 the projects following Harmattan.
 
-When starting the "Isnogud" project (say), the isnogud,
+When starting the "Isnogud" project (say), the isnogud-stable,
 isnogud-testing, and isnogud-proposed-updates distributions are added
 to the Maemo archive.  They are created by copying the corresponding
 Harmattan distributions.  Development then starts in isnogud-testing,
-without much regard to compatibility to isnogud if so desired.
+without much regard to compatibility to isnogud-stable if so desired.
 
 ** Delayed publication
 


More information about the maemo-commits mailing list