Hi, +1. There are countless fixes and stability improvements on the main development branch that would benefit the majority of users.
Breaking changes: there are some minor API breakages compared to 0.7, but there was an effort to avoid breaking core APIs and the configuration syntax. I agree with Marc that we should allow ourselves more freedom to fix issues even at the cost of breaking APIs, especially before 1.0. To allow the community some time to finalize the API, I would not rush 1.0 right after 0.8, unless we see that the API is stable and something we can commit to. Thanks, regards, Marton On Wed, 15 Jul 2020 at 17:36, Marc Parisi <phroc...@apache.org> wrote: > +1 to 0.8.0. Been keeping up with changes and I think the progress is > great. > > In my opinion the breaking changes are long coming and probably would be > appreciated by the community. > > Arpad are you thinking of going to 1.x? You're discussing 0.8, but is there > any reason to not jump to 1.x after that? > > Thanks, > Marc > > On Wed, Jul 15, 2020 at 10:12 AM Joe Witt <joe.w...@gmail.com> wrote: > > > Arpad > > > > Yep makes sense. Frankly the 0. versioning gives the flexibility to do > > these breaking changes during this stage of the lifecycle. > > > > Thanks > > > > On Wed, Jul 15, 2020 at 7:06 AM Arpad Boda <ab...@apache.org> wrote: > > > > > Hey, > > > > > > Quite a lot of time has passed since the last release and also a lot of > > > improvements and bug fixes have been made (Memleaks fixed, new > > threadpool, > > > some new processors, etc), so I think it's time for a new release. > > > > > > Another important aspect would be the release of the current state of > the > > > source before introducing some breaking changes - which seems to be > > > necessary at this point. > > > > > > What do you think? > > > > > > Thanks, regards, > > > Arpad > > > > > >
