<div class="gmail_quote"><div>So, once all those things are in place what Andrew says WILL happen?</div><div>I think plans as important as that deserves an announcement.</div><div>Roadmap for the project? Future directions for the main committers?</div>
<div>Are there patent issues?</div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Date: Mon, 11 Jul 2011 20:45:14 -0400<br>
From: Gregory Maxwell <<a href="mailto:gmaxwell@gmail.com">gmaxwell@gmail.com</a>><br>
Subject: Re: [CELT-dev] Mailing list and project shutdown<br>
announcement?<br>
To: Andrew Lentvorski <<a href="mailto:bsder@allcaps.org">bsder@allcaps.org</a>><br>
Cc: <a href="mailto:celt-dev@xiph.org">celt-dev@xiph.org</a><br>
Message-ID:<br>
<<a href="mailto:CAAS2fgSShUwdzPsGxPYy2cb42fRO0Pd9_uSc1Fyey1KWBGZBYA@mail.gmail.com">CAAS2fgSShUwdzPsGxPYy2cb42fRO0Pd9_uSc1Fyey1KWBGZBYA@mail.gmail.com</a>><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
On Mon, Jul 11, 2011 at 6:02 AM, Andrew Lentvorski <<a href="mailto:bsder@allcaps.org">bsder@allcaps.org</a>> wrote:<br>
> If everything has moved and this mailing list has gone dormant, how<br>
> about an official announcement as well as official pointers to the new<br>
> stuff?<br>
><br>
> It would also be good to have some sort of "migration document" given<br>
> that you have to do specific things to OPUS in order to get the old CELT<br>
> behavior.<br>
<br>
Hm. I think we're sort of in a weird limbo right now.<br>
<br>
The Opus codebase has major regressions in everything outside of the<br>
codec itself: build system, tests, tools useability, API, and<br>
licensing status all have issues that need to be cleared up.<br>
<br>
Once the IETF bitstream standardization hurdles are out of the way it<br>
will be easier to dedicate time to getting these issues resolved.<br>
<br>
Until then I'd feel bad making a heavy-handed push to the new stuff<br>
when it's not currently a drop in replacement due to these issues.<br>
<br></blockquote></div>