Currently, JobStatus (enumeration of possible job statuses) and RunStatus (enumeration of possible workflow statuses) reside in reana-db repo. But, the values that represent job and workflow statuses are used by workflow-engines and, as of now, are duplicated in each of them. The engines do not depend on reana-db so they cannot import those enums.
What do you think if we move JobStatus and RunStatus enums from reana-db to reana-commons repo? How will it affect future maintenance of engines, reana-db and reana-commons repositories?
Originated in this PR
Currently,
JobStatus(enumeration of possible job statuses) andRunStatus(enumeration of possible workflow statuses) reside in reana-db repo. But, the values that represent job and workflow statuses are used by workflow-engines and, as of now, are duplicated in each of them. The engines do not depend onreana-dbso they cannot import those enums.What do you think if we move
JobStatusandRunStatusenums fromreana-dbtoreana-commonsrepo? How will it affect future maintenance of engines,reana-dbandreana-commonsrepositories?Originated in this PR