Karaf Features Defined:
-4. Are all your project's features that are intended for release added to the features.xml and
+#. Are all your project's features that are intended for release added to the features.xml and
checked into integration git repository. Yes/No (please provide link to the gerrit patch)
#. List all top-level, user-facing, and stable Karaf features for your project.
Documentation:
-6. List the kinds of documentation you will provide including at least:
+#. List the kinds of documentation you will provide including at least:
* One user/operator guide section per user-facing feature.
* One developer guide per top-level feature.
* An installation guide for any top-level features that require more than ``feature:install
<feature-name>`` to install.
+ * Eventually, release notes, but it is a good idea to keep release notes as a living document
+ when significant changes others should be aware of are made.
* Optional tutorials and how tos.
-#. Have you checked in an AsciiDoc outline to the docs repository? Yes/No (link to gerrit patch)
+#. Have you checked in a reStructuredText outline for each of the documents you will provide
+ to the docs repository? Yes/No (link to gerrit patch)
Integration and Test:
-8. Have you started automated system testing for your top-level features. Yes/No
+#. Have you started automated system testing for your top-level features. Yes/No
* If yes, link to test report
* If no, why?
Project Specific:
-10. Were there any project-specific deliverables planned for this milestone? Yes/No
+#. Were there any project-specific deliverables planned for this milestone? Yes/No
* If so, were they delivered? Yes/No
Stables Features (Only for Projects with Stable Features)
-7. Do your stable features fulfill quality requirements (i.e. unit and/or integration test coverage
+#. Do your stable features fulfill quality requirements (i.e. unit and/or integration test coverage
of at least 75%)? (Yes/No)
* (If yes, link to sonar report)