Migration to mono-repo #437
Closed
darh
announced in
Announcements
Replies: 1 comment
-
Migrated. New, merged repository can be found here: We'll archive obsolete repos in a couple of days. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We are making some changes to our repository structure and will be moving to mono-repo, joining all webapps, discover server, english texts from
corteza-locale
and a few other bits and pieces.History from each repo will be squashed into a single commit.
All migrated repositories will be archived so we don't break links on old changelogs etc.
What will move where:
Location of the merged code (the mono-repo) will be under
cortezaproject/corteza
replacing the current code there.Why not merging Corredor?
Corteza does not require Corredor to run as it is not the part of core. Same argument could be used for discovery server but we decided to keep it closer for convenience.
Why not docs?
Docs changes follow different rhythm than the product. Also, access control policy is different.
Why only English and not the whole locale?
At the moment, we can only support english texts that come along with new features and fixes. And these locale changes need to be close (in the same repo) as the actual code changes.
This will be done on 2022.9.x branch and before branching out 2023.3.x.
We are currently testing and developing this in private repo to avoid confusion.
Beta Was this translation helpful? Give feedback.
All reactions