On Sat, Jun 15, 2019 at 01:17:51AM +0800, Paul Wise wrote:
> In order to implement the request below (hide some suggestions from
> tracker.d.o during the freeze (and possibly other things)), we need a
> machine-readable information source about the current stage of the
> freeze and what that means for new upstream releases. I suggest that
> this come in the form of a YAML/JSON file in the testing directory
> containing start dates for each stage of the freeze and an end date
> once that is known. Each stage could be accompanied by some sort of
> metadata about the freeze policy, so that the tracker could also give
> advice on what to upload and what not to upload.
>
> https://release.debian.org/testing/freeze.yaml
Here's a draft of what it could look like, does this satisfy the
requirements?
---
schema: 1
codename: "buster"
planned_release: "2019-07-06T12:00:00Z"
stages:
transition_freeze:
starts: "2019-01-12T00:00:00Z"
friendly_name: "Transition freeze"
explanation: "No more planned transitions are accepted after this date"
migrations: "auto"
url: "https://release.debian.org/buster/freeze_policy.html";
soft_freeze:
starts: "2019-02-12T00:00:00Z"
friendly_name: "Soft freeze"
explanation: "Extended ageing, no new source packages, no re-entry"
url: "https://release.debian.org/buster/freeze_policy.html";
migrations: "auto"
full_freeze:
starts: "2019-03-12T00:00:00Z"
friendly_name: "Full freeze"
explanation: "Targetted fixes only, manual review"
url: "https://release.debian.org/buster/freeze_policy.html";
migrations: "manual"
quiet_period:
starts: "2019-06-29T00:00:00Z"
friendly_name: "Quiet period"
explanation: "Pre-release quiet period with emergency fixes only"
url:
"https://lists.debian.org/debian-devel-announce/2019/06/msg00003.html";
migrations: "manual"
...
--
Jonathan Wiltshire j...@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
