ELT-Platform.md

@@ -10,20 +10,20 @@ Streams
 -------
 
 * **ELT Platform Next Stream** - The ELT Packages Collection is aimed at the next major release. It is a bleeding-edge development stream for ELT DevEnv and ECOS packages.
-  * Builds against multiple targets (Base OS).
+  * Built against multiple targets (Base OS).
   * No restrictions on update policy.
   * Broken packages are allowed.
   * No CI for that stream (with current infra state).
 * **Yearly Streams** - The ELT Packages Collection is aimed at the yearly public and biannual CCS releases. Yearly Streams are branched out from ELT Platform Next Stream. Quite stable development platform for higher level ELT Control Software Projects like IFW, RTCTK, HLCC, LSVs, and TREx.
-  * Build and tested against one target (Base OS).
+  * Built and tested against one target (Base OS).
   * Relaxed update policy.
   * Broken packages should be fixed fast.
   * Stream fully supported by CI.
 * **Release Streams** - The ELT Package Collection branched out from Yearly Stream or another Release Stream. The Release Stream is used to stabilize the release and deliver eventual patches and bug fixes.
   * The ELT DevEnv team provides infrastructure and support for two release streams yearly.
-    * Public release, and CCS release - owned by IFW, RTCTK, HLCC, and CCS.
+    * Public release - owned by all stakeholders.
     * CCS release - owned by CCS.
-  * The ELT DevEnv team may provide support and infrastructure for more release streams for a cost of 0.2 FTE covered by the requesting party.
+  * The ELT DevEnv team may provide support and infrastructure for more release streams for a cost of 0.25 FTE and extra computational resources needed, covered by the requesting party.
   * Strict update policy. Owners of a stream have exclusive rights to decide about updates.
   * Broken packages are not allowed.
   * Stream fully supported by CI.
@@ -34,10 +34,10 @@ Update Policy
 Each ELT Platform Stream type has a different update policy since they target different use cases.
 
 * **ELT Platform Next** 
-  * No restrictions on braking changes.
+  * No restrictions on breaking changes.
   * Ideally teams coordinate updates to avoid broken packages.
 * **Yearly Streams**
-  * Projects may introduce breaking changes only till the release date scheduled in yearly plan.
+  * Projects may introduce breaking changes only until the release date scheduled in yearly plan.
   * Breaking changes that are unanimously agreed between all affected ELT Platform projects are allowed.
   * Updates containing bug fixes and new features are allowed and can be merged at any time.
   * All updates have to pass staging pipelines before being provided to users.
@@ -49,7 +49,9 @@ Each ELT Platform Stream type has a different update policy since they target di
 Versioning
 ----------
 
-Each update of packages for ELT Platform Projects results in an OBS build that provides a consistent repository of RPM packages. For selected streams, such a repository is also a subject for staging pipeline verification. Each repository is published locally (at ESO), publicly (on ftp.eso.org), or both. Every such repository has its version. The versioning differs slightly depending on the stream type.
+Each update of packages for ELT Platform Projects results in an OBS build that provides a consistent repository of RPM packages. For selected streams, such a repository is also a subject for staging pipeline verification. Each repository is published locally (at ESO), publicly (on ftp.eso.org), or both. It is planned that some packages (ie. LSVs, TREx) will be published only internally and not available to the public. 
+
+Every such repository has its version. The versioning differs slightly depending on the stream type.
 
 **ELT Platform Next Stream**
 
@@ -92,10 +94,10 @@ Version: `<year>(.<parents_stream_ids>)+.<id>`
 
 * `<year>` - last two digits of the yearly parent stream.
 * `<parents_stream_ids>` - ids of parent streams.
-  * That part consists update ids of parent streams
+  * That part consists of update ids of parent streams
 * `<id>` - counter of updates.
   * starts with 0.
-  * each update to streams' packages increments it by 1.
+  * each update to streams packages increments it by 1.