Skip to content

Conversation

@nastena1606
Copy link
Collaborator

No description provided.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the release notes and documentation for version 0.7.0, including rebranding from PLM (Percona Link for MongoDB) to PCSM (Percona ClusterSync for MongoDB) and updates the copyright year to 2026.

  • Bumped version from 0.6.0 to 0.7.0 with release date of 2025-01-13
  • Rebranded product references from PLM to PCSM throughout configuration files
  • Added comprehensive 0.7.0 release notes documenting new features, improvements, and bug fixes

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File Description
variables.yml Updated version to 0.7.0, year to 2026, added v0.7.0 date, and rebranded from PLM to PCSM
mkdocs-base.yml Updated site name, copyright year, repository references, and navigation items to reflect PCSM branding
docs/release-notes/0.7.0.md Added new release notes for version 0.7.0 with features, improvements, and bug fixes

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


### Improvement

* [PCSM-200](https://perconadev.atlassian.net/browse/PCSM-200) - Support sharded collections with non-default collation
Copy link
Collaborator

@inelpandzic inelpandzic Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we have this one as a Improvement since it is actually part of the whole sharding feature? Like this I read it like we already supported sharded collection but now we improved it somehow.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would have a single item for sharding. But since epic is not yet ready completely, not sure what issue to include. @radoslawszulgo what's your take on this?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean, I don't have like a strong opinion on this, but just thought it could be a bit weird that we have a improvement for something that we didn't have in prev release, just that.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with Inel

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed this item

@@ -0,0 +1,61 @@
# {{ pcsm.full_name }} 0.7.0 ({{ date.v0_7_0 }})

We are excited to announce the general availability (GA) of {{ pcsm.full_name }} ({{pcsm.short}}) for data replication across replica sets. The GA status means {{ pcsm.short }} has passed the stability and reliability milestones required for enterprise use. You can confidently deploy it in production for data migration across replica sets with zero downtime.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
We are excited to announce the general availability (GA) of {{ pcsm.full_name }} ({{pcsm.short}}) for data replication across replica sets. The GA status means {{ pcsm.short }} has passed the stability and reliability milestones required for enterprise use. You can confidently deploy it in production for data migration across replica sets with zero downtime.
We are excited to announce the general availability (GA) of {{ pcsm.full_name }} ({{pcsm.short}}) for data replication across replica sets. The GA status means {{ pcsm.short }} has passed the stability and reliability milestones required for enterprise use. You can confidently deploy it in production for data migration across replica sets with near-zero downtime.


* [PCSM-200](https://perconadev.atlassian.net/browse/PCSM-200) - Support sharded collections with non-default collation

* [PCSM-238](https://perconadev.atlassian.net/browse/PCSM-238) - Added the information about a namespace an index belongs to to finalization stage logs
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* [PCSM-238](https://perconadev.atlassian.net/browse/PCSM-238) - Added the information about a namespace an index belongs to to finalization stage logs
* [PCSM-238](https://perconadev.atlassian.net/browse/PCSM-238) - Added the information about a namespace an index belongs to finalization stage logs

Copy link
Collaborator

@radoslawszulgo radoslawszulgo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good - few suggestions left

variables.yml Outdated
release: '0.7.0'

date:
v0_7_0: '2025-01-13'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
v0_7_0: '2025-01-13'
v0_7_0: '2025-01-14'


* [PCSM-230](https://perconadev.atlassian.net/browse/PCSM-230) - Fixed the issue with incorrect handling of exclude and include filtered during the filtered sync.

* [PCSM-237](https://perconadev.atlassian.net/browse/PCSM-237) - Resolved a race condition in the test finalization process that caused sporadic failures during the apply stage. No newline at end of file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* [PCSM-237](https://perconadev.atlassian.net/browse/PCSM-237) - Resolved a race condition in the test finalization process that caused sporadic failures during the apply stage.

This is related to our internal tests, there is no need to add it to release notes.


### Improvement

* [PCSM-238](https://perconadev.atlassian.net/browse/PCSM-238) - Finalization stage logs now include the namespace for each index
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

### New Feature

* [PCSM-195](https://perconadev.atlassian.net/browse/PCSM-195) - Added the ability to clone sharded collections
* [PCSM-207](https://perconadev.atlassian.net/browse/PCSM-207) - Expose MongoDB client operation timeout via env variable
Copy link
Contributor

@sandraromanchenko sandraromanchenko Jan 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PCSM-207 was a contribution, so need to add thanks to @balthazar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants