Em qua, 6 de fev de 2019 às 04:15, Frank Heckenbach
<f.heckenb...@fh-soft.de> escreveu:
>
> > Em qui, 3 de jan de 2019 às 22:56, Frank Heckenbach
> > <f.heckenb...@fh-soft.de> escreveu:
> > >
> > > According to https://release.debian.org/buster/freeze_policy.html:
> > >
> > > 2019-01-12 - Transition freeze
> > >
> > > Is there still time yet to get a fix in, or is it FUBAR already?
> >
> > Transition freeze means ABI changes in libraries are forbidden. We're
> > almost in soft-freeze now, more info at:
> > https://lists.debian.org/debian-devel-announce/2019/01/msg00008.html
>
> So do we have time until the soft freeze on 2019-02-12 (I hope not)
> or the full freeze (2019-03-12) to get a 2.4.0 uploaded?
I believe so, yes, maybe even for the soft freeze (I am not sure how
much the time shortens for migrating packages fixing important bugs,
it varies).
> > I have to review the situation again, I completely swapped it out of
> > my memory.
>
> My suggestion of 2018-11-25 still stands. But if you want me to do
> my part of it, please do your review quickly and tell me soon
> (or, if it's indeed necessary for the soft freeze, immediately) to
> avoid running out of time.
Your plan sounds OK. Changing packages after the release, with time,
should be OK. I can submit automatic bug reports for the affected
packages.
Maybe it would even be possible to have the applications set a global
variable, e.g.:
enum class Render { Default = 1, Basic };
FTGL->setRender(Render renderType);
and then the Render() function(s) would dispatch to either
RenderDefault() or RenderBasic() versions as appropriate?
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
