Skip to content

Release 1.0.1 #345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
viktorklang opened this issue Mar 13, 2017 · 63 comments
Closed

Release 1.0.1 #345

viktorklang opened this issue Mar 13, 2017 · 63 comments
Milestone

Comments

@viktorklang
Copy link
Contributor

I propose that we, @reactive-streams/contributors, release 1.0.1 on the 2-year anniversary of 1.0.0

No semantically breaking changes.

Improved TCK? Improved docs? Improved spec?

@viktorklang viktorklang added this to the 1.0.1 milestone Mar 13, 2017
@akarnokd
Copy link
Contributor

How urgent is this? I might have found an issue with PublisherVerification: some tests don't cancel the test Subscriber's Subscription which leaves the created Publisher hanging or leaking resources.

My suspects are the spec111_multicast_* because in my TestNG execution, the test required_createPublisher1MustProduceAStreamOfExactly1Element failed when the whole suite was executed but passed when the individual test was executed.

I'm currently preparing a TCK test that should detect if cancel was called in a particular test if there was no onComplete from the created Publisher.

@viktorklang
Copy link
Contributor Author

The 2-year anniversary is on the 29th of April :)

@smaldini
Copy link
Contributor

I'll be ready to publish it but i think it's a good idea. Could we reference in this ticket issues we are going to address (or label them) ? In particular would this come with the soft breaking about request(0) not erroring ?

@viktorklang
Copy link
Contributor Author

viktorklang commented Mar 24, 2017

@smaldini I'd love to discuss that "problem" (request(0)) but not on this Issue :)

I believe all tickets are assigned to the milestone.

(And thanks for volunteering to release!!)

@DougLea
Copy link
Contributor

DougLea commented Mar 24, 2017

Just FYI, jdk was successfully changed to reject request(0) for initial jdk9 release, even though I still think it was a bad idea. But better to conform to 1.0 spec anyway...

@viktorklang
Copy link
Contributor Author

Thanks @DougLea!

@viktorklang
Copy link
Contributor Author

@reactive-streams/contributors Has everyone updated their implementations to try the new TCK?
Are we good to go on promoting the RC1 to final? Please report back here ASAP.

@ktoso
Copy link
Contributor

ktoso commented Jul 3, 2017

Akka Streams passing: akka/akka#23267 👍

(Let's await some more impls to upgrade, at least 3 or 4 I'd say)

@akarnokd
Copy link
Contributor

akarnokd commented Jul 3, 2017

RxJava 2.1.2 snapshot passing: ReactiveX/RxJava#5453

ktoso added a commit to ktoso/vertx-reactive-streams that referenced this issue Jul 3, 2017
Please give the 1.0.1 Release Candidate 1 TCK a run so we can be sure it did not cause any unexpected regressions / changes.
See here for libraries updating to 1.0.1 process: reactive-streams/reactive-streams-jvm#345 
Thanks in advance!
@ktoso
Copy link
Contributor

ktoso commented Jul 3, 2017

I made a PR in Vert.X asking to check the RC: vert-x3/vertx-reactive-streams#9

@smaldini
Copy link
Contributor

smaldini commented Jul 3, 2017

I'll check in a moment today thanks @reactive-streams/contributors

@viktorklang
Copy link
Contributor Author

@smaldini Any verdict?

@DougLea Doug, have you had any chance to run the newer TCK on your SubPub?

@ktoso
Copy link
Contributor

ktoso commented Jul 4, 2017

FYI VertX did not reply on my ticket so far.

@smaldini
Copy link
Contributor

smaldini commented Jul 4, 2017

Give us one more day its one of those very few bank holiday in the US :)

@akarnokd
Copy link
Contributor

akarnokd commented Jul 4, 2017

JDK 9b176 via this:

37 tests done, 2 failed, 15 ignored

SubmissionPublisherTckTest.required_spec309_requestNegativeNumberMustSignalIllegalArgumentException

java.lang.AssertionError: Got expected exception [class java.lang.IllegalArgumentException] but missing message part [3.9], was: non-positive subscription request

SubmissionPublisherTckTest.required_spec309_requestZeroMustSignalIllegalArgumentException

java.lang.AssertionError: Got expected exception [class java.lang.IllegalArgumentException] but missing message part [3.9], was: non-positive subscription request

@DougLea
Copy link
Contributor

DougLea commented Jul 4, 2017 via email

@ktoso
Copy link
Contributor

ktoso commented Jul 4, 2017

Right, I guess we'll have to loosen up a bit - I'll handle that;
I think rule reference or "non-positive" string appearance should be fine

@viktorklang
Copy link
Contributor Author

@DougLea The text-match could be loosened—it is there to make sure that the IAE doesn't stem from something else (the alternative would be to introduce a new Exception type, which would IMO not pull its weight).

@viktorklang
Copy link
Contributor Author

@smaldini Ok :)

@viktorklang
Copy link
Contributor Author

1:9 and 2:13 do not mandate that the rule is referenced in the cause message so I think it'd actually be more reasonable to drop the requirement. Thoughts? (It is of course completely backwards compatible)

@ktoso
Copy link
Contributor

ktoso commented Jul 4, 2017

1:9 and 2:13 do not mandate that the rule is referenced in the cause message so I think it'd actually be more reasonable to drop the requirement. Thoughts? (It is of course completely backwards compatible)

Yeah, very good point. We even have to do so, otherwise the TCK would allow "not quite the spec abiding" impls to pass. Since the JDK's interfaces have their own style of messages, and will soon become the "main" interfaces, we should make sure they fit the rules (or rather, the rules in this case fit them).

Sanity checking: Yes, it's definitely backwards compatible - we require less from implementations now.

PRed separately from TCK change in case this requires more discussion, but seems pretty obvious: #386

@ktoso
Copy link
Contributor

ktoso commented Jul 7, 2017

3 day after reminder;
Ping @smaldini, were you able to upgrade? It does not take much time and we want to ship an RC2 with: #386 #385
So please give it a try and give those a look - thanks!

@smaldini
Copy link
Contributor

smaldini commented Jul 7, 2017

You should go ahead then with RC2 i'll batch update, sorry i'm in the middle of some widespread polishing that is loosely connected to RS (properly recognizing 1.3 and 3.9).

@ktoso
Copy link
Contributor

ktoso commented Jul 12, 2017

It was only staged, not closed, so won't get to central yet.
With 2 projects having confirmed artifacts are fine I think we can close/release it I think - i can click the button ;)

@viktorklang
Copy link
Contributor Author

@ktoso Yes please!

@ktoso
Copy link
Contributor

ktoso commented Jul 12, 2017

Shipping :shipit: Thanks Roland for preparing the artifacts and David for checking they're fine 👍

@rkuhn
Copy link
Member

rkuhn commented Jul 12, 2017 via email

@ktoso
Copy link
Contributor

ktoso commented Jul 12, 2017

No worries, let the businessing go well :-)

It's out: http://repo1.maven.org/maven2/org/reactivestreams/reactive-streams/1.0.1-RC2/

@viktorklang
Copy link
Contributor Author

@smaldini Any update on RC2? :)

@smaldini
Copy link
Contributor

smaldini commented Jul 13, 2017

Yup we;re good on our side, I removed some exceptions to the tck but I have 2 remaining one I need to investigate regarding two test expectations regarding a processor. Also I used the 3.1 to get back on track for spec we discussed (allowing onError on request), so we don't have this exception anymore like rxjava, good citizen again.
LGTM

@smaldini
Copy link
Contributor

smaldini commented Aug 3, 2017

So when do you think we shall proceed to GA ?

@ktoso
Copy link
Contributor

ktoso commented Aug 4, 2017

We're waiting for info if you're passing the TCK :-)

@smaldini
Copy link
Contributor

smaldini commented Aug 4, 2017

Oh yes we do!

@ktoso
Copy link
Contributor

ktoso commented Aug 4, 2017

Completely, right? Including the issues you mentioned above?
If so, then I think we're good to call the 1.0.1, at least IMHO :-)

@viktorklang
Copy link
Contributor Author

viktorklang commented Aug 4, 2017 via email

@smaldini
Copy link
Contributor

smaldini commented Aug 8, 2017

👍 We got back on track by adopting internal/external facing subscriber protocol so we respect the rules (especially the onError possible from request)

@akarnokd
Copy link
Contributor

akarnokd commented Aug 8, 2017

RxJava 2 ready for 1.0.1! 👍

@viktorklang
Copy link
Contributor Author

@rkuhn would you be able to do us the honors of cutting the release within the next 8h? From the following tag I just pushed: https://github.com/reactive-streams/reactive-streams-jvm/tree/v1.0.1

Let me know if you won't have time today and I'll try to sort it out some other way, ok? 👍

I'll prepare the website, then upload javadoc etc.

@rkuhn
Copy link
Member

rkuhn commented Aug 9, 2017

Yes, I’ll do it around lunch time.

@viktorklang
Copy link
Contributor Author

viktorklang commented Aug 9, 2017 via email

@rkuhn
Copy link
Member

rkuhn commented Aug 9, 2017

The artifacts are staged at https://oss.sonatype.org/content/repositories/orgreactivestreams-1032, please let me know when to release them.

@akarnokd
Copy link
Contributor

akarnokd commented Aug 9, 2017

👍 for release asap.

@viktorklang
Copy link
Contributor Author

Thanks @rkuhn, I'm currently working to make sure that website, documentation links etc are updated. Would you be OK with releasing them 4pm CEST? (That way I have an extra couple of hours to verify things over at my end)

@rkuhn
Copy link
Member

rkuhn commented Aug 9, 2017 via email

@viktorklang
Copy link
Contributor Author

@rkuhn Perfect, thank you!

@rkuhn
Copy link
Member

rkuhn commented Aug 9, 2017

So, shall I press the button now?

@viktorklang
Copy link
Contributor Author

Yes!

@akarnokd
Copy link
Contributor

akarnokd commented Aug 9, 2017

Will you or somebody post the 1.0.1 javadoc to

http://www.reactive-streams.org/reactive-streams-1.0.1-javadoc/

?

@viktorklang
Copy link
Contributor Author

viktorklang commented Aug 9, 2017 via email

@rkuhn
Copy link
Member

rkuhn commented Aug 9, 2017

The artifacts are on Maven Central.

@viktorklang
Copy link
Contributor Author

Excellent! reactive-streams.org has been updated, great work everyone!! 🎆🎆🎆🎆🎆🎂🎂😎

@ktoso
Copy link
Contributor

ktoso commented Aug 9, 2017

Excellent! 🎆
Kudos and thanks everyone :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants