backporting changes from 6.x to 5.x
Petr Salinger
Petr.Salinger at t-systems.cz
Fri Mar 3 13:47:07 UTC 2006
Hi!
> Aurelien asked me about backporting recent changes from 6.x to 5.x. My opinion
> is that in order to preserve 5.x package stability (remember that some people is
> using it in production environment), we should be very conservative about this
> branch, and always use 6.x (or later) for new features/hacks/etc.
May be also decent attempt on amd64 ?
On the other hand, given upstream schedule,
it might be better to focus on stabilizing FreeBSD 6.x
and use it for both i386 and amd64 in near future.
Jan 30: Freeze RELENG_5 and RELENG_6
Mar 20: Release FreeBSD 6.1
Apr 3: Release FreeBSD 5.5
Jun 12: Freeze RELENG_6
Jul 31: Release FreeBSD 6.2
Oct 23: Freeze RELENG_6
Dec 11: Release FreeBSD 6.3
Petr
BTW, what to do with mailing lists usage
(http://lists.debian.org/debian-bsd/2006/02/msg00113.html)
Swap them, leave it as is ?
More information about the Glibc-bsd-devel
mailing list