Hi Paul,
On 29-03-2020 10:26, Paul Wise wrote:
> On Sun, 2020-03-29 at 08:45 +0200, Paul Gevers wrote:
>
>> But wouldn't that be harder to find for tracker and other consumers?
>
> There is a symlink testing -> bullseye so this works:
>
>
On Sun, 2020-03-29 at 08:45 +0200, Paul Gevers wrote:
> But wouldn't that be harder to find for tracker and other consumers?
There is a symlink testing -> bullseye so this works:
https://release.debian.org/testing/freeze-and-release-dates.yaml
I'm not sure when it gets updated but I assume
On Sun, Mar 29, 2020 at 08:47:38AM +0200, Paul Gevers wrote:
> On 29-03-2020 08:45, Paul Gevers wrote:
> >> I would suggest putting it at a per-release URL:
> >> https://release.debian.org/bullseye/freeze-and-release-dates.yaml
> > But wouldn't that be harder to find for tracker and other
Hi,
On 29-03-2020 08:45, Paul Gevers wrote:
>> I would suggest putting it at a per-release URL:
>>
>> https://release.debian.org/bullseye/freeze-and-release-dates.yaml
>
> But wouldn't that be harder to find for tracker and other consumers?
> After all, the release name is also in there, so the
Hi Paul,
On 29-03-2020 01:29, Paul Wise wrote:
> On Sat, 2020-03-28 at 22:21 +0100, Paul Gevers wrote:
>
>> I have stripped some more from template in the other bug;
>
> Looks good, but the quiet_period URL points at a buster mail.
Ack.
>> the first version should appear soon at
>>
On Sat, 2020-03-28 at 22:21 +0100, Paul Gevers wrote:
> I have stripped some more from template in the other bug;
Looks good, but the quiet_period URL points at a buster mail.
> the first version should appear soon at
> https://release.debian.org/freeze-and-release-dates.yaml
I would suggest
On Thu, 2020-03-26 at 21:32 +0100, Paul Gevers wrote:
> maybe all the tracker needs is the freeze date and the release date.
I guess that would probably do it yeah.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Hi Pabs,
On 14-03-2020 00:33, Paul Wise wrote:
> Since the release team are going to be able to tell which packages are
> at which stage of the freeze, you could export the information
> (migrations: manual or x days) alongside the excuses for each package
> and the tracker could list that
On Fri, 2020-03-13 at 22:56 +0100, Paul Gevers wrote:
> I assume you have read the current freeze_policy [1]. As you have seen,
> we have introduced a new phase, where the automatic migration depends on
> the package. I'm not sure how easy it is to cover that information into
> a this template.
Hi Paul,
On 07-02-2020 03:01, Paul Wise wrote:
>> Let me try to come back to this bug when we have communicated the dates
>> and provide a prototype so we can see if it works.
>
> Great, no rush. There isn't much activity on tracker.d.o features anyway.
I assume you have read the current
On Thu, 2020-02-06 at 13:32 +0100, Paul Gevers wrote:
> That is mostly because they have not been settled 100% yet.
Sorry, I meant for the buster release, which is done now. There is
still data for the last wheezy point release but nothing for the freeze
for buster or bullsye; I thought the
Hi,
On 06-02-2020 12:25, Paul Wise wrote:
> On Thu, 2020-02-06 at 12:02 +0100, Paul Gevers wrote:
>
>> We already have a maintained agenda for the team [1]. Would it make
>> sense to use that somehow?
>
> That doesn't appear to have enough info right now, it contains only the
> unblock deadline
On Thu, 2020-02-06 at 12:02 +0100, Paul Gevers wrote:
> We already have a maintained agenda for the team [1]. Would it make
> sense to use that somehow?
That doesn't appear to have enough info right now, it contains only the
unblock deadline and not the other freeze data.
> I fear that having
Hi Paul,
On Sat, 15 Jun 2019 01:17:51 +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
14 matches
Mail list logo
