Catalog support for 19 builds. #324
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
@ericof @davisagli I'd like to meet and talk about this proposal and cookieplone roadmap in general. |
ericof
approved these changes
Jan 7, 2026
davisagli
approved these changes
Jan 11, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@davisagli @ericof
This is a small change, but it can be annoying, as soon we would start using the catalog in core (because everybody would have to add this file in their projects, otherwise, the build will fail when it finds a "catalog:" entry.
So, I have two proposals I already mentioned to you before.
The first one, is that we need to streamline the "re-generation" of projects, by saving the data somewhere (cookiecutter replay file would be ok). We tap into it, we assign a known place in the generated project, that we later re-read on demand, replay cookieplone with it. We could use repoplone for it, or just cookieplone command line.
Second, is that maybe we can write "upgrade steps" for cookieplone? Given a local version of the generated files (based on date, for example), we run all the pending upgrade steps, in a GS fashion.
make upgrade, oruvx repoplone upgradeWhat do you think?