Skip to content

Improve documentation for 0.4 release #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 6, 2016
Merged

Improve documentation for 0.4 release #2

merged 1 commit into from
Dec 6, 2016

Conversation

wachterjohannes
Copy link
Member

This PR improves documentation for 0.4 release

@wachterjohannes wachterjohannes force-pushed the enhancement/doc branch 3 times, most recently from 69190d4 to 1295ff9 Compare December 5, 2016 09:10

TaskScheduler
-------------
The ``TaskScheduler`` stores tasks and schedules Executions. Foreach tasks there
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

executions

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

foreach is not one english word, must be for each

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And it should be task instead of tasks

TaskScheduler
-------------
The ``TaskScheduler`` stores tasks and schedules Executions. Foreach tasks there
exists always on execution in the status ``planned``, ``running``. If the task
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

exactly one execution, or should that say something else?

The ``TaskScheduler`` stores tasks and schedules Executions. Foreach tasks there
exists always on execution in the status ``planned``, ``running``. If the task
will only one time it only get one execution at all. For recurring tasks the
execution will always generated for the next run time.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For recurring tasks a new execution will be generated when the old one is completed.?

- ``workload``: the workload will be passed to the handler
- ``intervall``:
- ``firstExecution``:
- ``lastExecution``:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would write another short explanation or remove the colons.

@wachterjohannes
Copy link
Member Author

@danrot fixed

@danrot danrot merged commit 16b8ff9 into master Dec 6, 2016
@danrot danrot deleted the enhancement/doc branch December 6, 2016 09:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants