Mention API is stable now library is in 1.0.0

(cherry picked from commit c48e8f6)

Author: acogoluegnes

Diff for: README.adoc

@@ -16,8 +16,11 @@ Please refer to the https://rabbitmq.github.io/rabbitmq-stream-java-client/stabl
 
 == Project Maturity
 
-The project is in development and stabilization phase.
-Features and API are subject to change, but https://rabbitmq.github.io/rabbitmq-stream-java-client/stable/htmlsingle/#stability-of-programming-interfaces[breaking changes] will be kept to a minimum.
+The library is stable and production-ready.
+
+== Versioning
+
+This library uses https://semver.org/[semantic versioning].
 
 == Support
 

Diff for: src/docs/asciidoc/overview.adoc

@@ -75,30 +75,19 @@ recovery and automatic re-subscription for consumers.
 
 == Versioning
 
-The RabbitMQ Stream Java Client is in development and stabilization phase.
-When the stabilization phase ends, a 1.0.0 version will be cut, and
-https://semver.org/[semantic versioning] is likely to be enforced.
+This library uses https://semver.org/[semantic versioning].
 
-Before reaching the stable phase, the client will use a versioning scheme of `[0.MINOR.PATCH]` where:
-
-* `0` indicates the project is still in a stabilization phase.
-* `MINOR` is a 0-based number incrementing with each new release cycle. It generally reflects significant changes like new features and potentially some programming interfaces changes.
-* `PATCH` is a 0-based number incrementing with each service release, that is bux fixes.
-
-Breaking changes between releases can happen but will be kept to a minimum.
 The next section provides more details about the evolution of programming interfaces.
 
 [[stability-of-programming-interfaces]]
 == Stability of Programming Interfaces
 
-The RabbitMQ Stream Java Client is in active development but its programming interfaces will remain as stable as possible.
-There is no guarantee though that they will remain completely stable, at least until it reaches version 1.0.0.
-
 The client contains 2 sets of programming interfaces whose stability are of interest for application developers:
 
 * Application Programming Interfaces (API): those are the ones used to write application logic.
 They include the interfaces and classes in the `com.rabbitmq.stream` package (e.g. `Producer`, `Consumer`, `Message`).
-These API constitute the main programming model of the client and will be kept as stable as possible.
+These API constitute the main programming model of the client and are kept as stable as possible.
+New features may require to add methods to existing interfaces.
 * Service Provider Interfaces (SPI): those are interfaces to implement mainly technical behavior in the client.
 They are not meant to be used to implement application logic.
 Application developers may have to refer to them in the configuration phase and if they want to customize some internal behavior of the client.