| Re: [che-dev] Che+Theia repositories |
With all the things in the same repo, a project might end up with bad backward compatibility and modularization.Single repo approach is not a reason for that, but it can be connected. We have been facing that in main Che repo with Che master + GWT IDE + UD integrations.But it is possible to design architecture and processes in a way to avoid these mistakes even with a single repo approach.I'm OK with either decision, just wanted to mention this thing to remind that we should keep an eye on the codebase to avoid such problems in the future.On Tue, Nov 20, 2018 at 12:27 PM Yevhen Vydolob <yvydolob@xxxxxxxxxx> wrote:--Hi all,During our work on making Che+Theia IDE as default one in Eclipse Che, we created set of Theia extensions and plugins. At the moment, all of them are placed in separate repositories under eclipse organization on GitHub.We, as a team, have concerns about that approach (keeping all Che specific plugins and extensions in separate repositories) and already faced some problems with maintaining, planning, tracking the issues. That's why we have an intention to consolidate all Che-Theia related extensions and plugins in one repository, and in future that repository may include also docker file and Che-Theia editor plugin.Are there any concerns or feedbacks on the idea, described above, please, share with us?_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev
--_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev