You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by da...@apache.org on 2018/03/19 13:39:34 UTC
[sling-whiteboard] branch master updated: Move Feature read/write
API to API section
This is an automated email from the ASF dual-hosted git repository.
davidb 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 8e3cd73 Move Feature read/write API to API section
8e3cd73 is described below
commit 8e3cd73e9a3908160430c4b586f84b08653a6095
Author: David Bosschaert <bo...@adobe.com>
AuthorDate: Mon Mar 19 13:39:11 2018 +0000
Move Feature read/write API to API section
---
featuremodel/requirements.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/featuremodel/requirements.md b/featuremodel/requirements.md
index 7c58c50..90bdeec 100644
--- a/featuremodel/requirements.md
+++ b/featuremodel/requirements.md
@@ -62,6 +62,9 @@ The feature model is about describing a feature, aggregating features to either
* SFM430 - The startup order of features and bundles must be part of the resulting aggregated application model.
* SFM440 - The feature model must support additional, optional information about the feature like a human readable title, a description, vendor and licensing information.
* SFM450 - The feature model must use a versioned descriptor format so that if the format evolves in the future users can state in feature model files what version they are written for.
+
+## API Requirements
+
* SFM460 - The feature model should provide an externally accessible API for reading and writing feature files.
## Analysis Requirements
--
To stop receiving notification emails like this one, please contact
davidb@apache.org.