Skip to content

Improvement: #2643

@LittleHuba

Description

@LittleHuba

What

Define an approach for bumping versions of dependencies.
Users struggle with constant bumping of our dependecies. This makes it hard to adopt S-CORE.

See meeting minutes:
https://github.com/orgs/eclipse-score/discussions/434

How

  1. Modules must align on versions of dependencies
  2. We should not always bump to the latest release of everything (what are the criteria?)
  3. We should roll out tooling to help users understand what they do when bumping

Estimates for realization

Short term point 1 and 2 of "how" should be sufficient. Low effort big gain.
Long term this will only work with 3 as well. But this is bigger effort.

Category

  • Affects Detailed Design

Requirements / Architecture

  • Requirements / Architecture are not affected by this change?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions