[DOC-13372]: Create release note for docs-server:7.2.8

modules/release-notes/pages/relnotes.adoc

@@ -1,5 +1,7 @@
 = Release Notes for Couchbase Server 7.2
 
+include::partial$docs-server-7.2.8-release-note.adoc[]
+
 include::partial$docs-server-7.2.7-release-note.adoc[]
 
 include::partial$docs-server-7.2.6-release-note.adoc[]

modules/release-notes/partials/docs-server-7.2.8-release-note.adoc

@@ -0,0 +1,103 @@
+
+
+[#release-728]
+== Release 7.2.8 (July 2025)
+
+Couchbase Server 7.2.8 was released in July 2025.
+This maintenance release contains fixes to issues.
+
+== Fixed Issues
+
+
+
+
+
+
+
+
+
+
+
+
+=== XDCR
+
+[#table-known-issues-728-xdcr, cols="10,40,40"]
+|===
+|Issue | Description | Resolution
+
+| https://jira.issues.couchbase.com/browse/MB-66650/[MB-66650]
+
+a| When modifying filter expressions or mapping configurations (explicit/migration), race conditions may prevent proper replication from the source. This can result in source bucket documents failing to replicate to the target bucket.
+
+To address this issue, the system now displays an alert when detecting replication resuming from  stale checkpoints. This alert notifies users to delete and recreate the affected replication.
+
+IMPORTANT: Do not dismiss this alert by pausing and resuming the replication, as this will hide the warning without resolving the underlying issue.
+
+| Issue resolved
+
+|===
+
+
+
+
+
+
+
+
+=== Index Service
+
+[#table-known-issues-728-index-service, cols="10,40,40"]
+|===
+|Issue | Description | Resolution
+
+| https://jira.issues.couchbase.com/browse/MB-65375/[MB-65375]
+
+| Couchbase Server 7.2.8 (build 8817) includes an indexing update with commit [66f6f1c](https://github.com/couchbase/indexing/commit/66f6f1c3f54c5003c005ffa1cdb59619ccb67b14) that introduces the setting of minimum and maximum iterations per temperature for the Replica Repair scenario (MB-65375). This adjustment ensures more efficient command execution by setting the maxIteration parameter during the CommandRepairBuild process. Verification of this update has been confirmed on version 7.2.8. The update advises adding a functional test to verify the ALTER INDEX operation of increasing replicas, based on steps outlined in parent ticket MB-65347. Further details and discussions can be referenced in MB-65347's comments.
+
+// Generated by [chatgpt:gpt-4o]
+| Issue resolved
+
+| https://jira.issues.couchbase.com/browse/MB-66034/[MB-66034]
+
+| Build couchbase-server-7.2.8-8844 includes an update addressing MB-66034, improving the smart batching of DCP tokens by considering only participating destination nodes. This ensures that node exclude values are taken into account, optimizing performance and resource allocation. The change is committed under 8f62d21, enhancing the efficiency and reliability of the indexing process. This enhancement is part of the broader efforts in the 7.2.x series to streamline operations and reduce unnecessary overhead.
+
+// Generated by [chatgpt:gpt-4o]
+| Issue resolved
+
+| https://jira.issues.couchbase.com/browse/MB-67116/[MB-67116]
+
+a| A race condition in the projector service  could cause a deadlock when closing streams with high mutation rates. The issue, present since version 7.2.2, didn't affect functionality but resulted in increased memory consumption as mutations in the pipeline couldn't be released properly. 
+
+With this fix, memory usage has been restored to normal levels.
+
+| Issue resolved
+
+| https://jira.issues.couchbase.com/browse/MB-67118/[MB-67118]
+
+| The update to Couchbase Server 8.0.0-3266 includes an enhancement to the indexing component with a commit that addresses the handling of "DropInstance" tokens. This involves the integration of "BigValueGet" in the `handleNewDropInstanceCommandToken` function as per indexing commit [ed34bc5]. Similarly, Couchbase Server 7.2.8-8917 incorporates these changes with indexing commit [bc03590] to backport the enhancement to version 7.2.8. The effort is linked to issue [MB-66975] for version 8.0.0 and [MB-67118] for the backport to version 7.2.8. Test coverage through unit tests suggests the changes are stable and ready for closure.
+
+// Generated by [chatgpt:gpt-4o]
+| Issue resolved
+
+|===
+
+
+
+
+=== Tools
+
+[#table-known-issues-728-tools, cols="10,40,40"]
+|===
+|Issue | Description | Resolution
+
+| https://jira.issues.couchbase.com/browse/MB-57755/[MB-57755]
+
+a| Beginning with Server 7.2.8/7.6.7, when installing on a Linux system using cgroups v1, Server will set the `memory.swappiness` cgroups parameter to `0` for the `couchbase-server` service slice. This ensures best performance without affecting any other services that may be running on the system.
+
+For Linux systems using cgroups v2 (which is the default for the more recent releases of most Linux distributions), there is no `memory.swappiness` parameter for individual service slices. Therefore it is still highly recommended to set kernel swappiness to `0` globally on each node, as explained in the documentation: [https://docs.couchbase.com/server/current/install/install-swap-space.html\|https://docs.couchbase.com/server/current/install/install-swap-space.html]
+
+| Issue resolved
+
+|===
+
+