Bug#930521: tracker.d.o: during freezes dont complain about packages only in experimental
Hi, On Mon, 17 Jun 2019, Paul Wise wrote: > I believe these are the appropriate changes: > > * ask to migrate non-RC/beta/etc to unstable when not in the freeze > * don't ask to package versions that are already in experimental > > Does that sound reasonable Raphael? Yes. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/ signature.asc Description: PGP signature
Bug#930521: tracker.d.o: during freezes dont complain about packages only in experimental
On Fri, 14 Jun 2019 13:10:42 + Holger Levsen wrote: > 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) The case we were talking about here is voctomix-outcasts: https://tracker.debian.org/pkg/voctomix-outcasts The version found by uscan is in experimental. I believe these are the appropriate changes: * ask to migrate non-RC/beta/etc to unstable when not in the freeze * don't ask to package versions that are already in experimental Does that sound reasonable Raphael? This is the current state of the voctomix-outcasts versions/actions: versions unstable: 0.8.0-1 exp: 0.9.1-1 action needed A new upstream version is available: 0.9.1 high A new upstream version 0.9.1 is available, you should consider packaging it. Created: 2019-05-25 Last update: 2019-06-17 07:07 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#930521: tracker.d.o: during freezes dont complain about packages only in experimental
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/msg3.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
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...@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
Bug#930521: tracker.d.o: during freezes dont complain about packages only in experimental
package: tracker.debian.org severity: wishlist x-debbugs-cc: debian...@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. Thanks for maintaining tracker.d.o! -- tschau, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
