Hey Henrik,

Thanks for the ping! I plan to open the release vote this week.

Best,
Alex

On Wed, Oct 29, 2025 at 7:33 AM Henrik Ingo <[email protected]> wrote:

> Cool.
>
> Yes, unplugging the dependency is valuable in its own right, I think
> there's pent up ideas in all of our heads once we can more flexibly work
> with the code. (I think I wrote some ideas down in another ticket too.)
>
> henrik
>
>
>
> On Wed, Oct 29, 2025 at 4:49 AM Denis Shchepakin <
> [email protected]>
> wrote:
>
> > Hello!
> >
> > I'm still working on the implementation. I spent some time deriving some
> > formulas for the algorithm, so it computes in quadratic time. The
> majority
> > of the code is done and I'm wrapping it up. I'm going to test it in the
> > current environment, so it should be compatible with the current version
> of
> > Otava. I would also like to do more changes later once python is
> upgraded.
> >
> > On Tue, Oct 28, 2025 at 6:53 AM Henrik Ingo <[email protected]> wrote:
> >
> > > Hi
> > >
> > > I realize conference season is in full swing, but wanted to ask how
> > things
> > > are going for Denis on the one hand with the e-divisive work, and then
> > Alex
> > > you had plans for a small cleanup release still?
> > >
> > > On the latter, is it correct understanding that this release is still
> > > intended to be compatible with the historical versions of Otava, and
> then
> > > after that we go and rip out the signal_processing dependency, upgrade
> > > python versions, etc?
> > >
> > > henrik
> > >
> > > --
> > > *nyrkio.com <http://nyrkio.com/>* ~ *git blame for performance*
> > >
> > > Henrik Ingo, CEO
> > > [email protected]                               LinkedIn:
> > > www.linkedin.com/in/heingo
> > > +358 40 569 7354                                 Twitter:
> > > twitter.com/h_ingo
> > >
> >
>
>
> --
> *nyrkio.com <http://nyrkio.com/>* ~ *git blame for performance*
>
> Henrik Ingo, CEO
> [email protected]                               LinkedIn:
> www.linkedin.com/in/heingo
> +358 40 569 7354                                 Twitter:
> twitter.com/h_ingo
>

Reply via email to