You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
=== [RC-FN-001] Allow hyphenated descriptor class names
2
+
3
+
* Date: 2025-10-28
4
+
* Context:
5
+
** The runtime compiler recently introduced stricter validation that rejected binary names containing hyphens.
6
+
** Java reserves `module-info` and `package-info` descriptors, and downstream uses rely on compiling them through the cached compiler.
7
+
** We must prevent injection of directory traversal or shell-sensitive characters while honouring legitimate descriptor forms.
8
+
* Decision Statement:
9
+
** Relax the class name validation to accept hyphenated segments such as `module-info` and `package-info`, while maintaining segment level controls for other characters.
10
+
* Notes/Links:
11
+
** Change implemented in `src/main/java/net/openhft/compiler/CachedCompiler.java`.
12
+
13
+
=== [RC-TEST-002] Align coverage gate with achieved baseline
14
+
15
+
* Date: 2025-10-28
16
+
* Context:
17
+
** The enforced JaCoCo minimums were 83 % line and 76 % branch coverage, below both the documentation target and the current test suite capability.
18
+
** Recent test additions raise the baseline to ~85 % line and branch coverage, but still fall short of the historical 90 % goal.
19
+
** Failing builds on the higher 90 % target blocks releases without immediate scope to add more tests.
20
+
* Decision Statement:
21
+
** Increase the JaCoCo enforcement thresholds to 85 % for line and branch coverage so the build reflects the present safety net while keeping headroom for future improvements.
22
+
* *Alternatives Considered:*
23
+
** Retain the 90 % requirement:
24
+
*** _Pros:_ Preserves the original aspiration.
25
+
*** _Cons:_ The build fails despite the current suite, causing friction for ongoing work.
26
+
** Keep legacy 83/76 % thresholds:
27
+
*** _Pros:_ No configuration change needed.
28
+
*** _Cons:_ Enforcement would lag the actual quality level, risking future regressions.
29
+
* *Rationale for Decision:*
30
+
** Setting the guard at 85 % matches the measurable baseline and ensures regression detection without blocking releases.
31
+
** The documentation and configuration now stay consistent, supporting future increments once more tests land.
32
+
* *Impact & Consequences:*
33
+
** Build pipelines now fail if coverage slips below the new 85 % thresholds.
34
+
** Documentation for requirement JRC-TEST-014 is updated to the same value.
0 commit comments