You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by cz...@apache.org on 2018/02/19 17:04:30 UTC
[sling-whiteboard] branch master updated: Add requirement about
feature processing ordering
This is an automated email from the ASF dual-hosted git repository.
cziegeler pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-whiteboard.git
The following commit(s) were added to refs/heads/master by this push:
new 24c06c5 Add requirement about feature processing ordering
24c06c5 is described below
commit 24c06c58830a048ada1ce2676d1eedd752e2f2dc
Author: Carsten Ziegeler <cz...@apache.org>
AuthorDate: Mon Feb 19 18:04:25 2018 +0100
Add requirement about feature processing ordering
---
featuremodel/readme.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/featuremodel/readme.md b/featuremodel/readme.md
index 27b7bec..29ce4dd 100644
--- a/featuremodel/readme.md
+++ b/featuremodel/readme.md
@@ -51,6 +51,7 @@ The feature model should meet the following requirements:
* SFM340 - The feature model must support controlling of the exported API as described in https://github.com/apache/sling-whiteboard/blob/master/featuremodel/apicontroller.md
* SFM350 - The feature model must support explicit ordering of features. It must be possible to provide this ordering in separate file.
* SFM360 - The feature model must support variables to be used throughout the model, avoiding the need to repeat the same value several times.
+* SFM370 - When features are aggregated, the ordering of the processing of those features needs to be predictable and stable.
## Tooling
The following requirements relate to tooling around the Feature Model.
--
To stop receiving notification emails like this one, please contact
cziegeler@apache.org.