eclipse-score / eclipse-score/communication
Improvement: Job to generate deprecated warnings report nightly
- Dominant language
- C++
- Stars
- 62
- Forks
- 97
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 72
Description
### What
We treat warnings as errors, but deprecation warnings is something that we do not want to treat as errors, otherwise we could not deprecate anything.
However, it is quite easy to end up with a lot of deprecation warnings without an overview of how many we have. Having a nightly job that collects such warnings, it will help us to have an overview.
### How
_No response_
### Estimates for realization
_No response_
### Category
- [ ] Affects Detailed Design
### Requirements / Architecture
- [x] Requirements / Architecture are not affected by this change?
Contributor guide
Research direction
No files, tests, or CI entry points are named. Start by locating the existing warnings-as-errors configuration and any scheduled jobs, then determine how deprecation warnings can be collected separately. Done means a nightly job produces an overview of deprecation warnings without treating them as errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100