+1 to what Allen said. Regarding 1.0, the main problem is backward compatibility expectations from semantic versions. With so many languages supported in thrift, basically if we ever make any breaking change from any of the language libraries we need to bump the major version to comply with semver, which can be problematic.
On Sat, Mar 5, 2022 at 6:41 PM Allen George <[email protected]> wrote: > Hi Jens - > > First off, thank you so much for your work on Thrift. You've been a > consistent maintainer for as long as I've been a member of this community. > > I think it's less a question about versions, and more about expectations. > Thrift has two major challenges: a wide language footprint (which means > that maintainers have to understand N different > languages/tools/build/publish systems) and a fairly thin maintainer base. > Given that, I suggest that we support at most the last released version, as > well as what's in the main/master. I understand that this may cause > inconvenience to the user community, but I think that users can choose to > fork the codebase and generate/use the artifacts they need for the older > versions they're using. > > Best, > Allen > > On Sat, Mar 5, 2022 at 1:31 PM Randy Abernethy <[email protected]> > wrote: > > > If the community wants to move to 1.0 I would support that. > > > > On Sat, Mar 5, 2022 at 3:11 AM Jens Geyer <[email protected]> wrote: > > > > > > > > Am 05.03.2022 um 12:06 schrieb Jens Geyer: > > > > Java and the compiler (for C#) > > > > > > > > > Well, compiler code is a full package ... so that would then be a full > > > 0.16.1 indeed. > > > > > > > > > > -- > > > > Randy Abernethy > > Managing Partner > > RX-M, [email protected] > > o 415-800-2922 > > c 415-624-6447 > > >
