Job Atomicity

Registered by Scott James Remnant (Canonical) on 2008-02-21

The basic operations on a job of start and stop are already atomic in the sense that they can be repeated in any order, and only the last one issued has any effect. This specification proposes extending their atomicity so that their side-effects such as environment they provide to a job are also atomic based around the commands.

Blueprint information

Status:
Complete
Approver:
Scott James Remnant (Canonical)
Priority:
Essential
Drafter:
Scott James Remnant (Canonical)
Direction:
Approved
Assignee:
Scott James Remnant (Canonical)
Definition:
Approved
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Scott James Remnant (Canonical) on 2008-03-03
Completed by
Scott James Remnant (Canonical) on 2008-03-03

Related branches

Sprints

Whiteboard

Implemented in trunk

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.