On Tue, 12 Jan 2010 00:30:24 +0100
Arnaud Launay <[email protected]> wrote:
> But, if I understand this announce correctly, the complete inn
> port will be dropped to oblivion.
Yes, and that shouldn't (and won't) happen.
> Wouldn't it be better to stabilize inn 2.5 (there's even a 2.5.1
> release out there, with a quite reactive support/dev team, to
> which this "bug" could be pushed and corrected), than to just
> drop inn entirely ?
I'm working on getting 2.5.1 in the tree (and fixing a USE=python and
some other issues while I'm at it).
jer