This came out of IRC and discussion on a Pulp3 MVP call...
In Pulp2 we had three "internal" periodic tasks [0] that would do things
like database maintenance. The "nice to have" maintained periodic tasks can
be left out of the Pulp3 MVP, but @mhrivnak identified that '
download_deferred_content'
In redmine, we do not currently have a reasonable state for a "Task" to be
in once it is complete. A task could be something like:
- update the Pulp website
- perform a packaging activity related to Pulp in Fedora
- create a detailed plan for how to implement something
As a reminder, here are
Today on a call an observation was made that Pulp3 does not need 'results'
for a task. All non-error info about what happened during a task is
associated with it's associated "Progress Report" objects [0].
Is there a use case where 'result' is meaningful that we preclude by
removing it?
I
Up for consideration: PUP-2 [0], which proposes using Google style
docstring conventions for Pulp 3. Some relevant discussion has already
happened on this task [1].
The ratification process for this PUP is defined by PUP-1 [2]. Votes will
be counted on Monday April 10 at 9pm UTC. Use [3] to
