Re: Release update: debian-installer, kernels, infrastructure, freeze, etch, arm
Adrian Bunk <bunk@stusta.de> wrote:
> It doesn't need to be an exact date, but someting like
> "third quarter of 2005" or "mid-2008" would help to avoid situations
> like the sarge C++ transition that was too early [1] or the more than
> two years old X11 that will ship with sarge (and that doesn't support
> all hardware supported by recent X.org releases) [2].
(snip)
> [1] the first birthday of gcc 3.4.0 is only a few days from now
The C++ ABI was broken with gcc 3.2.0. For most architectures, 3.4.0
doesn't change anything. Is your point anything other than "The Debian
release process is broken and you should get rid of testing"? If not,
we've heard that several times already. It doesn't need reiterating.
--
Matthew Garrett | mjg59-chiark.mail.debian.devel@srcf.ucam.org
Reply to:
- Prev by Date:
Re: Bug#250202: Standardizing make target for 'patch' and 'upstream-source'
- Next by Date:
crediting debconf translators, revisited
- Previous by thread:
Re: Release update: debian-installer, kernels, infrastructure, freeze, etch, arm
- Next by thread:
Re: Release update: debian-installer, kernels, infrastructure, freeze, etch, arm
- Index(es):