Hi, Ossama Khayat wrote: > [...] > > No way. Not 2 two days before the release. Not that it would have been > > possible earlier either (too much risk) > > What is if it is late? Is there any chance. I see everyday there are some RC > bugs coming and going. Because there is/was no time to test it throughly? 2.1 was released short *after* the initial freeze fwiw and 2.2.0 just a few days ago. There's a difference between fixing RC bugs or normal bugs or upgrading to a new release. > > FWIW, if you actually looked you would have seen that 2.2 snapshots > > and 2.2.0 are alredy available in experimental. > > Yes, but users won't use experimental, nor would any one recommend it. Not my problem. In any case, there will be a 2.2.x etch backport after etch is released and bpos infrastructure is ready, for those who want to try it. > Thanks, and sorry for the late notification. I didn't need the notification in any way. 2.1 and 2.2 never had a real chance to enter etch anyway. Notification for 2.2 stuff wasn't needed either since the packaging of it was done long ago and the security fixes were also backported long before the official 2.2.0 release. Gr??e/Regards, Ren? -- .''`. Ren? Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' rene@debian.org | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
Attachment:
signature.asc
Description: Digital signature