-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
Plip 3395 plone base #3396
Plip 3395 plone base #3396
Conversation
@jensens 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! |
I get strange tracebacks when I run a test. The test is chosen randomly, I just happened to have it in my bash history.
I think I saw a similar traceback recently, but can't remember what caused it. Well, might have been around the |
Slightly easier:
|
I confirm the tests pass locally (at least the ones that failed earlier for me). I have restarted the PLIP jobs. |
FTR: link to plip-jobs/3.9 https://jenkins.plone.org/view/PLIPs/job/plip-3395-plone.base-part-1-3.9/ |
And PLIP jobs are green! |
For me it would be good to merge. @plone/framework-team have a look at the implementation please. |
I had a look to the It seems well crafted but I have some doubts. The I also noted this That also feels weird, either we revert the deprecation or remove the code. That said I already asked if somebody of the @plone/framework-team has some time to review this one.
I would just say that you should feel free to push the merge button. |
One other thing... I think we lost some tests. It mentions |
Indeed. But this might get refactored later. OTOH defaultpage is used by a bunch of plone.app.* packages, so it has to be moved to somewhere. Probably to
This is true, but IMO out of scope here. We can tackle this on a different PR later. |
It seems in a former copy paste session the docstring was copied, but never reviewed. The test does not make any sense for |
@jenkins-plone-org please run jobs |
Oops, starting Jenkins via a comment here is not very useful. I stopped the jobs and started the proper PLIP jobs instead. |
All green. IMO ready for merge? |
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.
LGTM
see #3395