Skip to content

Clarify: versioning #785

Description

@AlexanderLanin

Versioning of individual "elements" is required for requirements only. Is that correct?

Todays implementation forces all elements to have a version, which does not match the process requirement.

Especially this does not make a lot of sense for automatically generated reports like the module verification report? As the report is assembled on the fly, and no diff appears in reviews, there is nothing that can be reviewed within a review. As the report includes pretty much everything in a specific repository, every change leads to a version increase?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions