As far as I can tell, as of v0.5.0,rlic.convolve is now feature complete, in the sense that it supports everything that was needed for adoption in known and active packages exposing a higher level API (yt, lick, and vegtarm).
However, the project is very young and I could imagine regretting some early decision still, so I'd like to keep some wiggle room for now.
It is also conceivable that I later want to expand the scope of the library to include post-processing functions, yet to be defined, that would allow downstream to ditch heavy dependencies like scipy or scikit-image.
In the mean time, I'd like to add a note to document the development status. In essence, I don't anticipate any API breaking changes, so rlic.convolve can be treated as stable, but other, experimental APIs could still be introduced before a 1.0.0
As far as I can tell, as of v0.5.0,
rlic.convolveis now feature complete, in the sense that it supports everything that was needed for adoption in known and active packages exposing a higher level API (yt, lick, and vegtarm).However, the project is very young and I could imagine regretting some early decision still, so I'd like to keep some wiggle room for now.
It is also conceivable that I later want to expand the scope of the library to include post-processing functions, yet to be defined, that would allow downstream to ditch heavy dependencies like
scipyorscikit-image.In the mean time, I'd like to add a note to document the development status. In essence, I don't anticipate any API breaking changes, so
rlic.convolvecan be treated as stable, but other, experimental APIs could still be introduced before a 1.0.0