Skip to content

DO NOT MERGE: run 'manage pip2buildout'#1090

Draft
mauritsvanrees wants to merge 4 commits into
6.2from
maurits-pip2buildout
Draft

DO NOT MERGE: run 'manage pip2buildout'#1090
mauritsvanrees wants to merge 4 commits into
6.2from
maurits-pip2buildout

Conversation

@mauritsvanrees

Copy link
Copy Markdown
Member

The first commits are small manual edits to prepare. And the last commit calls manage pip2buildout as a test for plone/plone.releaser#99. So see the last commit for the actual changes that are done by this command.

Later we can decide if we really do this. It would be for Plone 6.3.

Note that comments are removed. Some of those should then be manually moved from buildout files to pip/mxdev files.

Looks a bit less nice, but they will be removed by pip2buildout anyway.
Doing it by hand now, makes it much easier to see if pip2buildout makes any wrong changes.
This is currently in `checkouts.cfg`, but it will get removed when you call `manage pip2buildout`.
The setting has no equivalent in mxdev.
@mauritsvanrees

Copy link
Copy Markdown
Member Author

Let's check Jenkins for good measure.

@jenkins-plone-org please run jobs

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.

1 participant