Hi Paul, On Sat, 15 Jun 2019 01:17:51 +0800 Paul Wise <pabs@debian.org> 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 We already have a maintained agenda for the team [1]. Would it make sense to use that somehow? I fear that having an additional place (next to the freeze_policy document [2]) to store this is likely to get out of sync. Paul [1] http://release.debian.org/release-calendar.ics [2] https://release.debian.org/bullseye/freeze_policy.html
Attachment:
signature.asc
Description: OpenPGP digital signature