openstack/mistral
Code Issues Proposed changes

Remove achieved goals from the lis of annual goals

Browse Source 
Change-Id: Ie2a308e139a81c65943114a563569b44fd04b6f9
This commit is contained in:
Renat Akhmerov 2018-02-05 18:09:57 +07:00
parent b991844679
commit 0b28e30436
1 changed files with 1 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.rst
View File

@ -211,7 +211,7 @@ defined in the configuration file should only be used if ``all`` Mistral
servers are launched on the same process. Otherwise, messages do not get
delivered because the ``fake`` transport is using an in-process queue.
Project Goals 2017
Project Goals 2018
------------------
#. **Complete Mistral documentation**.
@ -225,19 +225,6 @@ Project Goals 2017
the same style and structure principles. The obvious sub-goal of this goal
is to establish these principles.
#. **Complete Mistral Custom Actions API**.
There has been the initiative in Mistral team since April of 2016 to
refactor Mistral actions subsystem in order to make the process of
developing Mistral actions easier and clearer. In 2017 we need to complete
this effort and make sure that all APIs are stable and it’s well-documented.
*Definition of done*:
All API interfaces are stable, existing actions are rewritten using this new
API, OpenStack actions are also rewritten based on the new API and moved to
mistral-extra repo. Everything is well documented and the doc has enough
examples.
#. **Finish Mistral multi-node mode**.
Mistral needs to be proven to work reliably in multi-node mode. In order
@ -248,10 +235,6 @@ Project Goals 2017
CI gate supports MySQL, all critically important functionality (join,
with-items, parallel workflows, sequential workflows) is covered by tests.
#. **Reduce workflow execution time**.
*Definition of done*: Average workflow execution time reduced by 30%.
Project Resources
-----------------