Change repository model for 3.0 #5518

Closed
opened 2026-01-22 15:09:48 +01:00 by admin · 1 comment
Owner

Originally created by @Koc on GitHub (May 2, 2017).

Originally assigned to: @Ocramius on GitHub.

Have you considered switching from multi-repositories to one monolith repo + git subtree split (like in Symfony) for 3.0? https://www.tomasvotruba.cz/blog/2017/01/31/how-monolithic-repository-in-open-source-saved-my-laziness/

Originally created by @Koc on GitHub (May 2, 2017). Originally assigned to: @Ocramius on GitHub. Have you considered switching from multi-repositories to one monolith repo + git subtree split (like in Symfony) for 3.0? https://www.tomasvotruba.cz/blog/2017/01/31/how-monolithic-repository-in-open-source-saved-my-laziness/
admin added the Won't FixQuestion labels 2026-01-22 15:09:48 +01:00
admin closed this issue 2026-01-22 15:09:48 +01:00
Author
Owner

@Ocramius commented on GitHub (May 2, 2017):

@Koc we had a single repository, but it was actually more trouble for us than anything else, and the stability constraints of the different repositories are different.

@beberlei has an entire talk about it at https://qafoo.com/talks/15_08_froscon_monorepos.pdf

@Ocramius commented on GitHub (May 2, 2017): @Koc we had a single repository, but it was actually more trouble for us than anything else, and the stability constraints of the different repositories are different. @beberlei has an entire talk about it at https://qafoo.com/talks/15_08_froscon_monorepos.pdf
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#5518