AcademySoftwareFoundation / AcademySoftwareFoundation/aswf-docker

Are ci-packages versions in versions.yaml no longer relevant for Conan packages?

Open
#310 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
189
Forks
42
Avg merge
9h 38m
Merged PRs (30d)
6

Description

In `versions.yaml` the `ci-packages` versions lists specific package versions, are those relevant for Conan packages, and can they be removed one the last packages are converted from Docker "packages" to Conan packages?

```
ci-packages:
clang:
- "1-clang6.2"
- "1-clang7.2"
- "1-clang8.2"
- "1-clang9.2"
- "1-clang10.2"
- "2-clang10.3"
- "2-clang11.4"
- "2-clang12.1"
- "2-clang13.1"
- "2-clang14.0"
- "3-clang14.2"
- "3-clang15.2"
- "4-clang16.4"
- "4-clang17.4"
- "5-clang18.3"
- "5-clang19.3"
- "6-clang19.1"
- "6-clang20.1"
ninja:
- "1.3"
- "2.2"
- "3.2"
- "4.4"
- "5.3"
- "6.1"
cmake:
- "1.3"
- "2.2"
...
```

Contributor guide

Open the contributing guide

Research direction

Start by reading versions.yaml and tracing where the ci-packages versions are consumed. Compare those uses with the remaining Docker-to-Conan package conversions, then determine whether the entries are still required. Done means the relevance is established and obsolete entries are removed only if no remaining package workflow depends on them.

Written by the indexing model from the issue text.

Assessment

Tech stack
cmake, docker
Domain
build-system
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.