Skip to content

Commit c7a1d4d

Browse files
author
Matt Howlett
committed
link to experimental branch
1 parent f7f8d4a commit c7a1d4d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,9 @@ dotnet add package -v 0.11.4 Confluent.Kafka
5454
### Development Branch
5555

5656
We have started working towards a 1.0 release of the library which will occur after we add idempotence and transaction features. In order to best accomodate these and other changes,
57-
we will be making breaking changes to the API in that release. You can track our progress on the `1.0-experimental` branch (as well as corresponding packages on
58-
[nuget.org](https://www.nuget.org/packages/Confluent.Kafka/)). We have already added an **AdminClient** as well as support for **message headers** and **custom timestamps** amongst other things.
59-
Note that all work on this branch is subject to change and should not be considered production ready. All feedback is very welcome!
57+
we will be making breaking changes to the API in that release. You can track our progress on the [1.0-experimental](https://github.com/confluentinc/confluent-kafka-dotnet/tree/1.0-experimental)
58+
branch (as well as corresponding packages on [nuget.org](https://www.nuget.org/packages/Confluent.Kafka/)). We have already added an **AdminClient** as well as support for **message headers**
59+
and **custom timestamps** amongst other things. Note that all work on this branch is subject to change and should not be considered production ready. All feedback is very welcome!
6060

6161
Also, nuget packages corresponding to all release branch commits are available from the following nuget package source (Note: this is not a web url - you should specify it in the nuget package manger):
6262
[https://ci.appveyor.com/nuget/confluent-kafka-dotnet](https://ci.appveyor.com/nuget/confluent-kafka-dotnet). The version suffix of these nuget packages matches the appveyor build number. You can see which commit a particular build number corresponds to by looking at the

0 commit comments

Comments
 (0)