You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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-db
so they cannot import those enums.What do you think if we move
JobStatus
andRunStatus
enums fromreana-db
toreana-commons
repo? How will it affect future maintenance of engines,reana-db
andreana-commons
repositories?Originated in this PR
The text was updated successfully, but these errors were encountered: