Closed thet closed 3 years ago
@thet 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:
@jenkins-plone-org please run jobs
With this simple comment all the jobs will be started automatically.
Happy hacking!
@jenkins-plone-org please run jobs
tnx
@mauritsvanrees I'm about to add another commit fixing some problems I found using check-manifest
Created last_compilation profile as only place with last_compilation values. Moved the last_compilation values out of the default profile. Then we do not need a complete profile when we add an upgrade step for updating the last_compilation date of a bundle. [mauritsvanrees]
Hide the upgrades package from site-creation and quickinstaller. This way, we do not need to add each new upgrade profile to the list of non installable products. [mauritsvanrees]
Upgrade to Mockup 4.0.2. [thet]
Register new icons. [thet]
These many files are only due to the "yarn install" step and the fact that we currently still have through-the-web compiling, which need all resources accessible via the web browser. This will go away with the ES6 branch - there we do not ship anymore with the whole node_modules directory. I'm looking forward to it!