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

未关闭
#129 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@nradakovic 已经在做这个了。

开始于 2026年8月26日。

评估

这个 Issue 还没有评估数据。

描述

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
主要语言
Starlark
星标
2
派生
11
平均合并
1 天 14 小时
30 天内合并 PR
10

贡献指南

这个仓库没有索引到贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

eclipse-score/bazel_cpp_toolchains 的其他 Issue

查看 eclipse-score/bazel_cpp_toolchains 的全部 Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。