Hi Sebastian,
[trimming bit recipents list + adding debian-kernel]
On Sat, Nov 02, 2024 at 06:35:53PM +0100, Sebastian Ramacher wrote:
> Dear toolchain, debian-installer, and image maintainers,
>
> We, as the release team, are aware that we are late with the
> announcement of the freeze timeline
Hello Andreas, lists,
On 30/11/2024 19:28, Andreas Tille wrote:
...
Additionally, I wonder if an automated test suite for the installer
might be helpful.
...
There is already some fully automated testing in place.
The d-i installer is used at least in 2 different modes: in the netinst
image
Andreas Tille (2024-11-30):
> Cyril Brulebois wrote on 2024-11-13:
> > I don't think they've been caught up in the temporary freezes (I'd
> > think the longest one last cycle was a little week, usually a few
> > days, sometimes just a few hours), so I've never taken the time to
> > adjust (1) the
Cyril Brulebois wrote on 2024-11-13:
> I don't think they've been caught up in the temporary freezes (I'd think
> the longest one last cycle was a little week, usually a few days,
> sometimes just a few hours), so I've never taken the time to adjust (1)
> the hints and (2) the tooling that makes su
Simon McVittie (2024-11-12):
> On Sat, 02 Nov 2024 at 18:35:53 +0100, Sebastian Ramacher wrote:
> > In trixie we will also freeze all packages that produce udebs
>
> Is it straightforward to give packages whose udebs are not yet in
> active use a semi-automatic exemption from this freeze, while s
On Sat, 02 Nov 2024 at 18:35:53 +0100, Sebastian Ramacher wrote:
> In trixie we will also freeze all packages that produce udebs
Is it straightforward to give packages whose udebs are not yet in active
use a semi-automatic exemption from this freeze, while still applying
other reasons they might b
On Sat, Nov 02, 2024 at 06:35:53PM +0100, Sebastian Ramacher wrote:
>...
> Milestone 3 (Milestone 2 + 1 month): Soft freeze
>
> As with bookworm, with the soft freeze only small and targeted fixed are
> appropriate. Also, packages not in testing are blocked from migration to
> testing.
>...
I'd s
Apologies if this is a dumb question ...
On Sat Nov 2, 2024 at 6:35 PM CET, Sebastian Ramacher wrote:
> packages instead. We would like to get input from debian-boot to define
> the relevant criteria so that the freeze is useful for them. We would
> start with the following set
>
> packages prod
On Sat, Nov 02, 2024 at 06:35:53PM +0100, Sebastian Ramacher wrote:
>...
> Milestone 1: Toolchain and d-i freeze
>
> As in bookworm, we start with the freeze of toolchain with the goal to
> stabilize build essential packages and compilers and interpreters of
> major ecosystems (Python, Ruby, Rust,
[To trimmed, since this is probably only interesting to Rust and RT people]
On Sat, Nov 2, 2024, at 6:35 PM, Sebastian Ramacher wrote:
> Dear toolchain, debian-installer, and image maintainers,
>
> We, as the release team, are aware that we are late with the
> announcement of the freeze timeline f
Hi,
Thanks for contacting maintainers impacted by the new timeline scheme.
On 2024-11-02 18:35, Sebastian Ramacher wrote:
> Dear toolchain, debian-installer, and image maintainers,
>
> We, as the release team, are aware that we are late with the
> announcement of the freeze timeline for trixie.
Hi,
Sebastian Ramacher (2024-11-02):
> Dear toolchain, debian-installer, and image maintainers,
>
> We, as the release team, are aware that we are late with the
> announcement of the freeze timeline for trixie. After some internal
> discussions on how we want to handle the freeze for trixie base
12 matches
Mail list logo
