| 1 |
On Tue, 12 Jan 2010 00:30:24 +0100 |
| 2 |
Arnaud Launay <asl@××××××.org> wrote: |
| 3 |
|
| 4 |
> But, if I understand this announce correctly, the complete inn |
| 5 |
> port will be dropped to oblivion. |
| 6 |
|
| 7 |
Yes, and that shouldn't (and won't) happen. |
| 8 |
|
| 9 |
> Wouldn't it be better to stabilize inn 2.5 (there's even a 2.5.1 |
| 10 |
> release out there, with a quite reactive support/dev team, to |
| 11 |
> which this "bug" could be pushed and corrected), than to just |
| 12 |
> drop inn entirely ? |
| 13 |
|
| 14 |
I'm working on getting 2.5.1 in the tree (and fixing a USE=python and |
| 15 |
some other issues while I'm at it). |
| 16 |
|
| 17 |
|
| 18 |
jer |
Archives