Noticia aparecida en http://libuntu.wordpress.com/, original de rmarquez

Luego del reciente anuncio del lanzamiento de la segunda actualización de Debian 7.0 “Wheezy”, los desarrolladores han anunciado que la próxima versión de esta popular y gran distribución Linux, Debian 8.0 “Jessie”, estará entrado a la fase Freeze Feature en noviembre del 2014.

Debian 8 entrará en Freeze Feature noviembre 2014

A partir del 5 de noviembre del 2014, Debian 8.0 “Jessie” no recibirá nuevas características y funciones, ya que la próxima versión de Debian estará entrado a fase “freeze Feauter”.

Durante esta fase, los desarrolladores aplicaran varias políticas como por ejemplo la imposibilidad de subir nuevos paquetes o remoción de los mismos, no permitirán añadir nuevas funciones o características, así como removerlas en los paquetes, y mas si son paquetes nativos y únicamente recibirán parches de arreglos críticos que sean necesarios en los paquetes que anteriormente fuesen admitidos.

2014

También se han propuesto varias metas para Debian 8 “Jessie” como:

- Soporte nativo para systemd en cada paquete a través del script sysv
- Fortalecer los binarios ELF
- Hacer de clang un compilador secundario
- Depurar y limpiar los archivos piuparts
- SELinux
- UTF-8

Para conocer mas detalles de este anuncio, deberás remitirte al anuncio oficial:

(Por cierto, no es por ser troll, pero es increíble que algunos en su costumbre de copy paste ni siquieran sepan leer bien lo que copian.)
debian

Freeze date and Freeze Policy for Jessie
========================================

We are happy to announce that we will freeze Jessie at 23:59 UTC on
the 5th of November 2014.

To avoid any confusion around exactly how we will freeze, we have
prepared a draft of the Jessie Freeze Policy in advance
[FREEZE_POLICY].

Notable changes to the policy include:
* Well-defined stages in the freeze policy at certain dates.
- After 3 months of freeze, we will no longer allow removed
packages to re-enter testing
- We only accept fixes for important bugs in the first month.
- etc.
* Proactive automated removals 3 months into the freeze.
- Note that bug-free packages will be removed if they
(build-)depend on a RC-buggy, non-key package.
- Also note the interval of 7 days between each removal run.
* Inclusion of "do" and "don't" guidelines for uploads and unblock
bugs.
* Currently, we are undecided whether to maintain "carte blanche"
freeze exceptions at the start of the freeze. For now,
exceptions are *not* included in the freeze policy (i.e. do
*not* rely on them).
This means that changes have to migrate to testing *before* the
freeze date if they are to be included in the release.
- *If* such exceptions are added, they will *not* apply for
packages where migration would change the "upstream" version.
- Native packages are at a disadvantage here, since all uploads
of native packages are considered a new "upstream" version.
- It should go without saying, but "urgency" abuse is not
an acceptable way of getting your latest changes into the
release.
- It should also go without saying that embedding a new upstream
release in a patch just to get a such "carte blanche"
exception is also considered abuse.

As noted we are dealing with a draft, so there may be changes to the
actual freeze policy. Should we change the policy in a substantial
way, this will be included in subsequent "bits".



Linux