eclipse-score / eclipse-score/score

C/C++ Policies for S-CORE Release v1.0

Open
#3,252 0 comments 0 reactions 1 assignee Claimed by @nradakovic View on GitHub
Dominant language
Starlark
Stars
109
Forks
105
Avg merge
22h 15m
Merged PRs (30d)
22

Description

## Summary
Prepare and publish `score_cpp_policies` for the S-CORE `v1.0` release.

This product increment tracks the release readiness work for the S-CORE C/C++ coding policy repository. The repository provides reusable Bazel configuration and policy definitions for enforcing and standardizing C/C++ compiler options, warnings, and related development policies across S-CORE projects.

## Goal
Deliver a release-ready `score_cpp_policies` version aligned with the S-CORE `v1.0` release, including validated policy definitions, updated documentation, and reproducible configuration.

## Scope
The release should cover:
TBD

## Proposed Deliverables
- Release tag/version for `score_cpp_policies` aligned with S-CORE `v1.0`
- Reviewed and updated C/C++ policy definitions
- Verified Bazel integration and policy application
- Successful test workspace validation for relevant configurations
- Updated release-facing documentation
- Release notes summarizing supported policies, changes, and known limitations

## Validation Expectations
Before closing this issue, verify:
- Bazel integration works as expected for supported configurations
- C/C++ policies can be applied to supported targets
- Compiler options and warning configurations are correctly propagated
- Policy behavior is consistent across supported compilers and platforms
- Example targets build successfully with the release configuration
- Known compiler- or platform-specific limitations are documented

## Acceptance Criteria
- A releasable `score_cpp_policies` version is identified and tagged for S-CORE `v1.0`
- Supported C/C++ policies are validated in the example/test workspace
- Policy definitions and configuration are reviewed and up to date
- Documentation reflects the final release surface
- Known gaps, compiler-specific behavior, or unsupported scenarios are explicitly documented

## Checklist
- [ ] Confirm target release version and tag naming
- [ ] Review supported C/C++ policy matrix for `v1.0`
- [ ] Review and update compiler options and warning policies
- [ ] Validate Bazel integration and policy application
- [ ] Validate supported compiler configurations
- [ ] Validate supported platform configurations
- [ ] Review test/example targets and build results
- [ ] Review policy defaults and configuration outputs
- [ ] Update README/docs for the released surface
- [ ] Prepare release notes
- [ ] Publish/tag release

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.