The documentation for each SDK is kept in a single AsciiDoc file:
Tasks to prepare release notes (the process is the same on all platforms):
-
Copy the "Bugs" and "Known Issues" list from raw.html to the SDK’s Source File Location under the
== Release Notes
heading. Example: 24ba5e5 -
Review the issue summaries.
-
Commit on the release branch.
-
Push to GitHub.
Tasks for a minor release (x.y):
-
Clone repository
# replace *x.y* accordingly git clone [email protected]:couchbase/docs-couchbase-lite.git cbl-x.y cd cbl-x.y
-
Create new branch
release/x.y
and push to GitHub.git checkout -b release/x.y git push
-
Update metadata version. Example: 6171d62
-
Update your local playbook. Example:
... - url: ./../sg/sg-x.y branches: HEAD
-
Verify it builds locally
-
Update staging playbook. Example: 2d40527
-
Update production playbook. Example: 65958c9
-
Mark
release/x.y
as default branch on GitHub.
Tasks for a patch release:
-
Create new branch.
-
Bump
:version:
attribute in swift.adoc. Example: 939c8a2 -
Prepare Release Notes.
-
Open PR when there is code freeze for the release (tracked on JIRA).
-
Merge PR when the release is being published (tracked on JIRA).
-
Create new branch.
-
Bump
:version:
attribute java-jvm.adoc. Example: deefb02 -
Prepare Release Notes.
-
Open PR when there is code freeze for the release (tracked on JIRA).
-
Merge PR when the release is being published (tracked on JIRA).
-
Create new branch.
-
Bump
:version:
attribute java-android.adoc. Example: deefb02 -
Prepare Release Notes.
-
Open PR when there is code freeze for the release (tracked on JIRA).
-
Merge PR when the release is being published (tracked on JIRA).
-
Create new branch.
-
Prepare Release Notes.
-
Open PR when there is code freeze for the release (tracked on JIRA).
-
Merge PR when the release is being published (tracked on JIRA).
-
Create new branch.
-
Prepare Release Notes.
-
Open PR when there is code freeze for the release (tracked on JIRA).
-
Merge PR when the release is being published (tracked on JIRA).