Skip to content

Fix reference to base version and formatting #466

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

Merged
merged 2 commits into from
Aug 19, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CopyrightWaivers.txt
Original file line number Diff line number Diff line change
Expand Up @@ -44,3 +44,5 @@ kiiadi | Kyle Thomson, [email protected], Amazon.com
jroper | James Roper, [email protected], Lightbend Inc.
olegdokuka | Oleh Dokuka, [email protected], Netifi Inc.
Scottmitch | Scott Mitchell, [email protected], Apple Inc.
retronym | Jason Zaugg, [email protected], Lightbend Inc.

4 changes: 2 additions & 2 deletions RELEASE-NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@

## Announcement:

We—the Reactive Streams community—are pleased to announce the immediate availability of `Reactive Streams 1.0.3-RC1`. This update to `Reactive Streams` brings the following improvements over `1.0.3-RC1`.
We—the Reactive Streams community—are pleased to announce the immediate availability of `Reactive Streams 1.0.3-RC1`. This update to `Reactive Streams` brings the following improvements over `1.0.2`.

## Highlights:

Expand Down Expand Up @@ -66,7 +66,7 @@ We—the Reactive Streams community—are pleased to announce the immediate avai

*The intent of this rule is to establish that external synchronization must be added if a Subscriber will be using a Subscription concurrently by two or more threads.*

**1.0.3-RC1:* A Subscriber MUST ensure that all calls on its Subscription's request and cancel methods are performed serially.
**1.0.3-RC1:** A Subscriber MUST ensure that all calls on its Subscription's request and cancel methods are performed serially.

*The intent of this rule is to permit the calling of the request and cancel methods (including from multiple threads) if and only if a happens-before relation between each of the calls is established.*

Expand Down