You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository contains the third generation of the Couchbase SDKs on the JVM ("SDK 3").
15
15
@@ -36,7 +36,7 @@ and [Kotlin](https://docs.couchbase.com/kotlin-sdk/current/hello-world/overview.
36
36
These include getting started guides.
37
37
38
38
## Building
39
-
Stable releases are published on [maven central](https://search.maven.org/search?q=com.couchbase.client).
39
+
Stable releases are published on [Maven Central](https://central.sonatype.com/namespace/com.couchbase.client).
40
40
41
41
You can always also just build it from source, using any JDK 17+:
42
42
@@ -82,14 +82,32 @@ They are not included in the build by default as they require a) JDK 17 and b) t
82
82
To use a performer, uncomment the lines in the top-level pom.xml after 'Uncomment next lines to include the FIT performers', and reload the Maven config.
83
83
Then run one of the performers in an IDE.
84
84
85
-
### Branches & Release Trains
85
+
### Branches & Tags
86
86
87
-
Since this monorepo houses different versions of different artifacts, release train names have been chosen
88
-
to identify a collection of releases that belong to the same train.
87
+
Since version 3.9.0, this repository uses a mono-versioning strategy.
88
+
Each component in the monorepo is released with the same version number.
89
89
90
-
These trains are named after historic computers for your delight.
90
+
Releases are tagged by version number.
91
+
For example, version 3.9.0 is tagged as `3.9.0`.
91
92
92
-
Tags in each branch are named `branchname-ga` for the initial GA release, and then subsequently `branchname-sr-n` for
93
+
The `master` branch is where development for the next minor release happens.
94
+
95
+
Maintenance branches are named `<major>.<minor>.x`.
96
+
For example, the maintenance branch for minor version 3.9 is named `3.9.x`.
97
+
98
+
Instead of committing directly to a maintenance branch, first commit to `master` and then cherry-pick to the maintenance branch if possible.
99
+
100
+
#### Prior to version 3.9.0
101
+
102
+
Component versions before 3.9.0 were tagged as `<component>-<version>`.
103
+
For example, to check out the code for version 3.6.0 of the Java client, use tag `java-client-3.6.0`.
104
+
105
+
Before mono-versioning, this repository used release train code names
106
+
to identify a collection of related release versions.
107
+
108
+
These trains were named after historic computers for your delight.
109
+
110
+
Tags in each branch were named `branchname-ga` for the initial GA release, and then subsequently `branchname-sr-n` for
93
111
each service release. See the tag information for specifics of what's in there.
0 commit comments