New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.3.x Hotfix20200121 Password #3025
Conversation
@gotcha thanks for creating this Pull Request and help improve Plone! To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass. Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:
With this simple comment all the jobs will be started automatically. Happy hacking! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved.
I have added the tests to your branch.
@jenkins-plone-org please run jobs |
@mauritsvanrees Thanks for the tests ! What is the practice for changelog ? Does |
No. But you can do |
@mauritsvanrees Should I squash commits before merging ? a single commit might be easier to cherry-pick on other branches. |
161c4f3
to
c0c1913
Compare
Include Hotfix 20200121 with tests
c0c1913
to
96e8a55
Compare
There were two test failures. One is actually good: code was trying to set a password of three characters, which worked until now, but not anymore. I updated the test and force pushed it. |
@jenkins-plone-org please run jobs |
Password strength checks were not always checked
see #3021
better branch name, supercedes #3022