So there is a real regression related to the fact that passwords are contained in pages and so having the comparison returning false lead to merge conflicts when upgrading extensions that contains passwords. In general I believe we shouldn't compare the password values at all when performing equality checks of pages: it's possible that now we migrated password to their own property class and we don't rely anymore to StringClass it's easier to filter them out. However we also need to ensure that saving objects with a password without changing its value won't suddenly randomly override it, and in the contrary that it's still possible to change their value through object editor.
So we need to be careful where the equality works and where it doesn't and we probably need to review the APIs we're using to set password values.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.