Bug#930521: tracker.d.o: during freezes dont complain about packages only in experimental
Control: clone -1 -2
Control: reassign -2 release.debian.org
Control: retitle -2 release.debian.org: provide machine-readable
information about the freeze period for each release
Control: block -1 by -2
Hi Release Team,
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
On Fri, Jun 14, 2019 at 9:15 PM Holger Levsen wrote:
> package: tracker.debian.org
> severity: wishlist
> x-debbugs-cc: debian-qa@lists.debian.org
>
> On Thu, Jun 06, 2019 at 09:19:14PM +0800, Paul Wise wrote:
> > On Thu, Jun 6, 2019 at 6:20 PM Holger Levsen wrote:
> [tracker.d.o tells me that]
> > > - new upstream version only available in experimental (yes, because
> > > buster is frozen)
> >
> > I think it is appropriate to file a bug asking that this be disabled
> > when the freeze is on. As far as I can tell there is no
> > machine-readable indicator that buster is frozen, but there used to be
> > one for stretch in the release team's calendar file. So this would
> > require the release team to create a machine-readable way for the
> > tracker to know if testing is currently frozen.
> >
> > https://release.debian.org/release-calendar.ics
>
> filing a bug for this as suggested.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Reply to: