[Spice-devel] [PATCH] make celt to be optional

[Ron]

Hi Marc-André,

On Tue, Jun 12, 2012 at 09:59:39AM -0400, Marc-André Lureau wrote:
> ----- Mensaje original -----
> > On Tue, Jun 12, 2012 at 09:11:24AM -0400, Marc-André Lureau wrote:
> > > As long as the bitstream is not frozen, we can't use opus, or we
> > > will
> > > have the same problems as with celt today.
> >
> > As I understand it, while the bitstream is not officially frozen yet,
> > it's
> > very unlikely to change before the real freeze (unless big last
> > minute
> > issues are fine), so an Opus mode (marked as "no compat guarantees,
> > use at
> > your own risk, ...") will probably not cause significant
> > compatibilities issues.
> 
> That's just guesses. It's not about library API, but about bitstream.
> There is no guarantee. Sticking to celt051 is still a safer alternative.
> Otherwise, how would you identify almost-frozen bitstream to frozen bitstream?
> You would have to identify by library version (erk!)
> and be compatible with the old and new bitstram (which might be complicated
> depending on library design), or be incompatible with the intermediate version,
> situation which we better avoid!

The bitstream has been frozen for just a tad under a year now.
The API is frozen.

The working group and IETF last calls are over.

The IESG telecon has been held and has approved passing this.

The only thing we're effectively waiting on before the RFC is officially
published now is for this to pass through -editors.  And they aren't going
to edit anything that changes the API or bitstream.

Fedora is shipping Opus packages now, as is Debian.

Are there any other guesses that you would like informed answers to ;?


> > > Sadly, I think debian folks aren't looking at what is really
> > > celt051.
> >
> > It's not really an old and unmaintained release of celt ?
> 
> If something would show up, the spice team would
> certainly update it. So I wouldn't say unmaintained.
> 
> That's also what I would call a stable release.

So if say, a later version of celt was found to have issues, which were
fixed in that later version, and which led normally very reliable upstream
developers to suggest that at least some earlier versions may be at risk
of being crashed remotely ...  then what would you do?

Given that nobody is working on celt *at all* anymore, and there are no
simple patches being produced for this that you can Just Apply to it, how
exactly would you plan to "certainly update it"?  Since the only "certain"
update is not bitstream compatible with the celt you currently use.

<hint: this isn't a hypothetical question>

Stable releases have maintainers.  Celt no longer has a maintainer of
any description.  There is an important distinction there.

I'm not suggesting you need to panic and do anything silly.  But the time
to start addressing the real future of this _is_ now.


 Cheers,
 Ron