eclipse-score / eclipse-score/score

Release v0.9 common checklist

Open
#3,186 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Starlark
Stars
109
Forks
105
Avg merge
1d 9h
Merged PRs (30d)
21

Description

### Checklist (per Module)

- **Status per target module**
- [x] Baselibs (0.2.12)
- [x] Communication (0.4.0)
- [ ] Persistency (0.3.5) (@antonkri to double check)
- [ ] Orchestrator (0.1.1) (@pawelrutkaq should be removed)
- [ ] Kyron (0.1.3) (@pawelrutkaq to switch to 1.4)
- [x] Lifecycle (0.5.0)
- [ ] Logging (---) (@arsibo to create a new release)
- [ ] Time (---) (@lavrovvalera to create a new release)
- [ ] Config Management (@antonkri to double check)
- **Status per tooling module**
- [ ] crates (0.0.11) (@pawelrutkaq will check and may be raise to 0.0.12 in ref-int)
- [x] itf (0.5.0)
- [x] tooling (2.0.2) (ok for 0.9, for 0.10 we need to start working on migration to 2.1.0 as this brings a breaking change for ref_int -> @PiotrKorkus )
- [x] platform (0.7.1)
- [x] bazel_platforms (1.0.0)
- [x] test_scenarios (0.4.1)
- [ ] docs-as-code (8.0.1) (@AlexanderLanin should be switched to a newer version, e.g. 8.1.0)
- [x] process_description (2.1.2)
- [x] bazel_cpp_toolchains (0.5.4, @antonkri raise this topic for next release, as modules may need to change a lot of things to migrate to the newer version)

### Checklist (per Release)
- [ ] Module verification report
- https://github.com/eclipse-score/docs-as-code/pull/763
- Should be integrated for v0.9 for baselibs, persistency, logging. @antonkri will prepare a PR
- [ ] DR-8 implementation
- https://github.com/eclipse-score/reference_integration/pull/278 -> merged
- https://github.com/eclipse-score/reference_integration/pull/280 -> in Progress
- [ ] Release notes -> @antonkri
- [ ] Regenerate Overall_Status.rst -> @antonkri
- [ ] Create Release
- https://github.com/eclipse-score/reference_integration/pull/320

### Acceptance Criteria (DoD)
...

All modules fulfill the checklist

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the per-module and per-release checklists in this issue, then review the linked docs-as-code and reference_integration pull requests, especially #763, #278, #280, and #320. Done means the listed modules and release tasks are complete and all modules fulfill the checklist, but the issue's acceptance criteria are not yet specified beyond that.

Written by the indexing model from the issue text.

Assessment

Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.