mirror of
https://github.com/HDFGroup/hdf5.git
synced 2026-09-25 04:09:44 +03:00
Scot Breitenfeld
31d9d3c322
* Fix release-progress badges to read native issue-level Priority field The Project Priority board field was consolidated into a Priority field managed at the issue level (GitHub's org-wide custom issue fields), which the GraphQL API mirrors into projects as ProjectV2ItemIssueFieldValue instead of ProjectV2ItemFieldSingleSelectValue. The badge script's query had no fragment for that type, so it silently found zero priority values and would raise ProjectFieldMissingError on every run. * Show TBD on the Next Release badge when no milestone due date is set Previously the badge silently omitted any due-date annotation when the milestone had none, which read as if the badge just hadn't picked one up. * Update release-schedule image and plantuml source from add-next-release-badge branch * Don't flag CODEOWNERS auto-assignment as a manual reviewer add on a PR's first pass GitHub's own CODEOWNERS engine fires an identical review_requested webhook (sender type User, not Bot) when it auto-assigns owners at PR-open time. If one of those survives the cancel-in-progress race as the run that actually executes, it was mistaken for a human deliberately requesting that reviewer, permanently flagging them "manually added" and requiring separate approval — e.g. a catch-all "*" owner also named on a touched area's CODEOWNERS line got flagged on every PR touching that area, even though no human ever picked them. Gate the manual-add detection and the sticky per-area assignment on !isFirstCoordinationPass (no checklist comment posted yet), since that's exactly the window where GitHub's own auto-assignment is indistinguishable from a real human pick.
40 lines
1.0 KiB
Plaintext
40 lines
1.0 KiB
Plaintext
The release timeline was generated on PlantUML (https://plantuml.com)
|
|
|
|
The current script:
|
|
|
|
@startgantt
|
|
|
|
title HDF5 Release Schedule
|
|
|
|
projectscale monthly
|
|
Project starts 2023-01-01
|
|
|
|
[1.8] starts 2023-01-01 and lasts 5 weeks
|
|
[1.8.23 (EOL)] happens 2023-01-31
|
|
[1.8] is colored in #F76969
|
|
|
|
[1.10] starts 2023-01-01 and lasts 39 weeks
|
|
[1.10.10] happens 2023-03-31
|
|
[1.10.11 (EOL)] happens 2023-09-30
|
|
[1.10.11 (EOL)] displays on same row as [1.10.10]
|
|
[1.10] is colored in #F6DD60
|
|
|
|
[1.12] starts 2023-01-01 and lasts 48 weeks
|
|
[1.12.3 (EOL)] happens 2023-11-30
|
|
[1.12] is colored in #88CCEE
|
|
|
|
[1.14] starts at 2023-01-01 and lasts 110 weeks
|
|
[1.14.1] happens at 2023-04-30
|
|
[1.14.2] happens at 2023-08-31
|
|
[1.14.3] happens at 2023-10-31
|
|
[1.14.5] happens at 2024-09-30
|
|
[1.14.6 (EOL)] happens at 2025-01-30
|
|
[1.14.1] displays on same row as [1.14.1]
|
|
[1.14.2] displays on same row as [1.14.1]
|
|
[1.14.3] displays on same row as [1.14.1]
|
|
[1.14.5] displays on same row as [1.14.1]
|
|
[1.14.6 (EOL)] displays on same row as [1.14.1]
|
|
[1.14] is colored in #B187CF
|
|
|
|
@endgantt
|