Feature requests, improvements and bug tickets for S-CORE Release v1.0

Open
#129 0 comments 0 reactions 1 assignee View on GitHub

@nradakovic is already working on this.

Since Aug 26, 2026.

Assessment

This issue has not been assessed yet.

Description

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.0 release
  • 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.0 release

Checklist

  • Review open feature requests
  • Review open improvement tickets
  • Review open bug tickets
  • Identify release-blocking issues
  • Prioritize remaining v1.0 work
  • Ensure all applicable tickets are linked to this issue
  • Review unresolved tickets before release
  • Confirm release scope and known limitations
Dominant language
Starlark
Stars
2
Forks
11
Avg merge
1d 14h
Merged PRs (30d)
10

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-score/bazel_cpp_toolchains

All issues in eclipse-score/bazel_cpp_toolchains

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.