Develop automation support in support of release management

[tanjadegroot]

Problem description
The RM team validates that API assets meet the RM requirements.
A number of these checks could be automated if linting rules or other automation support could be developed.

Expected action
Develop linting rules or other automation support to be applied by the API sub projects for checking release management requirements.

There may be a different set of linting rules/automations for release management than for API development, and possibly also separate sets for M3 and M4 reviews.

For an item to be covered, please add a sub issue with its description.

We are looking for programmers to help with the implementation.

[tanjadegroot]

Open an issue in the Tooling project

[trehman-gsma]

I'm interested in supporting. Is there a list of requirements?

[tanjadegroot]

Have lot's in mind but need to write them :-)

[tanjadegroot]

All, please add your ideas on requirements for the input to the tooling issue to be created

[tanjadegroot]

We keep this issue to track automation requests to the tooling repo, but actual issues can be directly opened in tooling repo and added here.

[hdamker]

The issue camaraproject/tooling#9 needs feedback from Release Management (@tanjadegroot)

[tanjadegroot]

done

[tanjadegroot]

Rafal has created the page for further requirements capture here: https://lf-camaraproject.atlassian.net/wiki/x/GYADC

Not sure if we can close this issue ? and the tooling issue #9 ?

[hdamker]

Not sure if we can close this issue ? and the tooling issue #9 ?

The issue here you might can close ... or leave open, if we want to have a trigger in RM to follow the progress in tooling.
Instead of #9 I suppose you meant camaraproject/tooling#9 ... that I would keep open, as it is the task at hand.

[tanjadegroot]

Instead of #9 I suppose you meant camaraproject/tooling#9 ... that I would keep open, as it is the task at hand.

Yes indeed.

I will keep this issue open until camaraproject/tooling#9 is closed.

[hdamker]

Please see my comment on camaraproject/tooling#9 and the update of the wiki page. I propose that we either close the issue here or on tooling. As the requirements are related to the general release process and its meta-data I propose to keep it here in ReleaseManagement and close in tooling (keep there the concrete tools and its issues).

The comment from camaraproject/tooling#9 copied here:

I reworked the page https://lf-camaraproject.atlassian.net/wiki/x/GYADC. It defines the (new) CAMARA release process as a series of workflow categories (C1–C5). Each category the page defines what is validated or generated, where it happens (main, release, or maintenance branch), and how automation enforces consistency.

The original content of the page is preserved in the backup, mapped into these categories.

The wiki page is helpful for the next steps and should be continued.