Unsubscribe On Wed, Dec 2, 2020, 07:05 Xue Junkai <[email protected]> wrote:
> That's a good question. Those new features will be included in 1.0.x next > release. We planned to have it early next quarter. Since there are a lot of > new features than 0.9.x branches, we would like to have the features well > tested. > > BTW, 0.9.9 is still in the voting process, not officially released yet. > > Best, > > Junkai > > On Tue, Dec 1, 2020 at 8:33 PM Brent <[email protected]> wrote: > >> One more follow-up on this...is there a 1.0.x updated version release >> planned soon? >> >> For example, I noticed that the cluster topology API (i.e. the >> HelixAdmin.getClusterTopology() function and the >> org.apache.helix.api.topology package in helix-core) exists in the master >> branch and exists in the 0.9.9 tag, but does not exist in the 1.0.1 tag or >> the release-1.0.1 branch. Is it reasonable to expect that functionality >> and API to be ported forward soon? Or is that API going to be one of the >> backward-incompatible changes? >> >> I'm currently relying on the 1.0.1 binary release (e.g. >> http://mirrors.ibiblio.org/apache/helix/1.0.1/binaries/) and the 1.0.1 >> helix-core version on Maven central ( >> https://mvnrepository.com/artifact/org.apache.helix/helix-core/1.0.1) >> and they don't seem to have that code included. >> >> Thanks again! I'm enjoying getting to dig into Helix more deeply and see >> what it's capable of. >> >> On Mon, Nov 30, 2020 at 4:12 PM Brent <[email protected]> wrote: >> >>> Thank you, that makes a lot of sense. I will stick with 1.0.1 then. >>> >>> The pending issue I linked is not something PR-able (I don't think) >>> since it has to do with the published binary release, but if I encounter >>> anything else I will certainly consider creating a PR. Thanks again! >>> >>> On Mon, Nov 30, 2020 at 3:57 PM Xue Junkai <[email protected]> wrote: >>> >>>> Thanks Brent! I would suggest you to use 1.0.1 instead of using >>>> 0.9.x... Here're the two reasons: >>>> 1. 0.9.x releases are maintaining releases for the ones not upgrading >>>> to 1.0+. There will only be on demand / critical fixes. If you need >>>> advanced features, such as WAGED and other developing features. You have to >>>> bump up your version finally >>>> 2. 1.0+ versions have backward incompatible changes compared to 0.9.x. >>>> If you started with 0.9.x, you have to refactor your codebase once you >>>> decide to bump the version up to 1.0+ to use new features. >>>> >>>> For the pending issues, if you are interested, feel free to investigate >>>> it and submit PRs to Helix. We would like to see more and more people >>>> contributing to Helix! >>>> >>>> Best, >>>> >>>> Junkai >>>> >>>> On Mon, Nov 30, 2020 at 3:48 PM Brent <[email protected]> >>>> wrote: >>>> >>>>> Hey all, >>>>> >>>>> For a new project, what's the recommended version of Apache Helix to >>>>> use? >>>>> >>>>> I had originally been experimenting with 1.0.1, but between the recent >>>>> releases of 0.9.8 and 0.9.9 as well as some pending 1.0.1 issues (e.g. >>>>> https://github.com/apache/helix/issues/1387), I'm wonder if I should >>>>> be on the latest 0.9.x version instead. Thoughts? >>>>> >>>>> Thanks! >>>>> >>>>
