Release a new version?

[viktorklang]

Hi all,

given that Reactive Streams has been relicensed, we should publish a new set of artifacts under the new license.

So the options we have:

A) Release a 1.0.3 PATCH release with only the license change beyond the 1.0.3 code
B) Release a 1.0.4 version with the current master/HEAD under the new license
C) Release a 1.1.0 version with the current master/HEAD under the new license
D) Release a 2.0.0 version with the current master/HEAD under the new license

@reactive-streams/contributors Thoughts? Ideas? Preferences?

[akarnokd]

B

I'd reserve 2.0.0 for a more substantial expansion of the API.

[rkuhn]

Wouldn’t option D artificially split the ecosystem without any real reason to do so? I’m not a lawyer, so as a physicist I’d propose the evidence-based approach of considering this licensing change to be non-breaking until proven otherwise. Proof would have to arrive in the form of relevant complaints, reaching this repository after we do A or B. I’d propose a poll but unfortunately I’m not aware of a useful medium for conveying such a request (i.e. if we ask Twitter we may get an assortment of answers without learning much).

[simonbasle]

I'd vote for B as well

[OlegDokuka]

B

[ktoso]

"I am not a lawyer" prefaced, but... I don't see this change as needing a full major number: B sounds good to me.

[DougLea]

Considering that this is being done solely for lawyers, votes without a "IANAL" disclaimer should carry more weight! I have no preference.

[barchetta]

Any ETA on this? Thanks!
Bump

[viktorklang]

@reactive-streams/contributors Seems like the broad consensus is around option B—"1.0.4"

I'm currently in the process of setting up a completely new dev environment, so it would be very much appreciated if another contributor would be able to cut and publish that release. Any takers?

[barchetta]

Any news on 1.0.4?

[Nivedithaneethu]

@viktorklang Is there any ETA on releasing a new version with the latest license?
Thanks

[viktorklang]

@Nivedithaneethu Apologies for the delay, @rkuhn would you be able to cut this release together with me?

[rkuhn]

I don’t think I still have publishing credentials, at least I can’t find them — I haven’t worked in the JVM ecosystem since 2016.

[viktorklang]

https://github.com/reactive-streams/reactive-streams-jvm/pull/538/files

[viktorklang]

Reactive Streams 1.0.4 has been released.