> Considering the flaws in the previous release, is there a way for us to > mark it as deprecated?
I'm guessing we don't need to mark them as deprecated. Those releases work as expected, just missing docs. On Mon, Nov 20, 2023, at 17:23, Chojan Shang wrote: > +1. > > As we are facing these issues, it is appropriate to release a new > version promptly as a remedy. > > Considering the flaws in the previous release, is there a way for us to > mark it as deprecated? > > Best, > PsiACE > ________________________________ > From: Xuanwo <[email protected]> > Sent: Monday, November 20, 2023 00:04 > To: [email protected] <[email protected]> > Subject: [DISCUSS] Release Apache OpenDAL(incubating) 0.43.0 > > Hello, Apache OpenDAL(incubating) Community, > > This is a call for a discussion to release Apache OpenDAL(incubating) > version 0.43.0 > > The change lists about this release: > > https://github.com/apache/incubator-opendal/compare/v0.42.0...main > > I understand it's rather soon to initiate another release just four > days later, but numerous urgent issues require our immediate attention: > > - core/python/nodejs binary releases are all failed, we have to handle > them by hand. > - the docs for opendal core v0.42 built failed due to serval issues. > > I want to initiate a new release to address these issues, ensuring > we're on the correct trunk. > > Please leave your comments here about this release plan. > > Thanks > > Xuanwo -- Xuanwo
