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
For the purposes of our internal rosdistro and associated release process, the developed/maintained status values are not meaningful, and we'd prefer to use other keywords here. For example, development, testing, blocked, ready, etc.
Obviously they're fixed in the source in response to them being defined in the REP, but I wonder if you'd consider a patch which allows a field in the index.yaml (or maybe distribution.yaml) to override the list of acceptable statuses?
The text was updated successfully, but these errors were encountered:
That sounds reasonable to me. Afaik code which uses the status information only uses the string values but none of the defined enums (e.g. in the build farm). So the code parsing the distribution file might be the only location where valid_statuses is being used. Therefore I would pick distribution.yaml to keep the information self contained.
For the purposes of our internal rosdistro and associated release process, the
developed
/maintained
status values are not meaningful, and we'd prefer to use other keywords here. For example,development
,testing
,blocked
,ready
, etc.Obviously they're fixed in the source in response to them being defined in the REP, but I wonder if you'd consider a patch which allows a field in the
index.yaml
(or maybedistribution.yaml
) to override the list of acceptable statuses?The text was updated successfully, but these errors were encountered: