icecast-dev, now that the means of communication seem to be more stable again, i would like to call upon all developers of icecast, ices, libshout and the other related tools and projects to bring together the work that has been done in the last months and to move on. to get an overview of what has happened and what needs to be done, i started to add a Development section in the wiki pages of icecast[1] and ices[2] - please correct, add and extend. what about further releases? libshout2.1 - icecast2.1 - ices2.1 which features have to be in there? j [1] http://wiki.xiph.org/Icecast [2] http://wiki.xiph.org/Ices
On Sep 19, 2004, at 12:58 PM, j@v2v.cc wrote:> icecast-dev, > > now that the means of communication seem to be more stable again, > i would like to call upon all developers of icecast, ices, libshout > and the other related tools and projects to bring together the work > that > has been done in the last months and to move on.FWIW, I have been running icecast HEAD that I checked out of svn on 25 August and it's been running like a champ on Solaris 9. I have some code changes I'd like to submit for consideration, mainly concerning stream statistics and logging. I'll try to get around to that later this next week after doing some further refinement. /dale
On Sunday, 19 September 2004 at 18:58, j@v2v.cc wrote:> what about further releases? libshout2.1 - icecast2.1 - ices2.1 > which features have to be in there?The libshout trunk code has new features that would merit a 2.1 release (multi-codec Ogg support and a non-blocking API), but I don't think it makes any sense to do this until the implementation has been better tested. Probably the best way to do this would be to port ices 2 to the libshout trunk.