Feature requests, improvements and bug tickets for S-CORE Release v1.0
@nradakovic ci sta già lavorando.
Dal 26/8/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Summary
Track feature requests, improvements, and bug fixes required for the S-CORE v1.0 release that are not associated with a dedicated Epic.
This issue provides a central overview of smaller release-related tasks and ensures that relevant work is identified, prioritized, and completed before the v1.0 release.
Larger work items with their own dedicated Epic should remain tracked under their respective Epics and are not required to be duplicated here.
Goal
Ensure that all identified small feature requests, improvements, and bug fixes required for the S-CORE v1.0 release are tracked and resolved before the release.
Scope
This issue covers:
- Small feature requests
- Improvements and refinements
- Bug fixes
- Documentation fixes or improvements
- Build, CI, and developer-experience improvements
- Other release-blocking or release-relevant tasks that do not justify a dedicated Epic
Tracking
Tasks should be linked to this issue when they:
- Are targeted for the S-CORE
v1.0release - Do not have another Epic as their parent
- Can be addressed as an independent, relatively small work item
Tasks that grow beyond the scope of a small change should be moved to a dedicated Epic where appropriate.
Acceptance Criteria
- All identified release-relevant small tasks are linked to this issue
- Each linked task has a clear description and acceptance criteria
- Release-blocking issues are identified and prioritized
- All required tasks are completed or explicitly reviewed and accepted as known limitations before the
v1.0release
Checklist
- Review open feature requests
- Review open improvement tickets
- Review open bug tickets
- Identify release-blocking issues
- Prioritize remaining
v1.0work - Ensure all applicable tickets are linked to this issue
- Review unresolved tickets before release
- Confirm release scope and known limitations
- Lingua principale
- Starlark
- Stelle
- 2
- Fork
- 11
- Merge medio
- 1g 14h
- PR unite (30g)
- 10
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di eclipse-score/bazel_cpp_toolchains
-
eclipse-score/bazel_cpp_toolchains#147 · 1 assegnatario ·
-
action config documentation feature improvements p3 template
eclipse-score/bazel_cpp_toolchains#138 · 1 commento · 1 assegnatario ·
-
blocked bug p2 toolchain pkg
eclipse-score/bazel_cpp_toolchains#68 · 27 commenti · 1 assegnatario ·
-
bug feature p3 template wip
eclipse-score/bazel_cpp_toolchains#53 · 1 assegnatario ·