3 ms·
Well, actually there are two JEPs: - Migrate from Mercurial to Git - https://openjdk.java.net/jeps/357 https://openjdk.java.net/jeps/357 - Migrate to GitHub -
by krzyk 6y ago
Well, actually there are two JEPs:
- Migrate from Mercurial to Git - https://openjdk.java.net/jeps/357 https://openjdk.java.net/jeps/357
- Migrate to GitHub - https://openjdk.java.net/jeps/369 https://openjdk.java.net/jeps/369
And also in JEP 369 at the and there is:
> In order to prevent the Skara tooling from depending upon a particular provider's API, support for multiple external providers has been a strict requirement from the beginning. All of the tooling is also required to work with the open-source GitLab Community Edition (GitLab CE).
- WhyNotHugo 6y agoI wonder why they didn't pick GitLab though. They just mention it as an alternative, but there's not a single word on why they preferred one over the other.
- Alupis 6y agoBecause "Github is where it's at!". They're looking for an instantly-large community with built in support. Everyone has a Github account, but not everyone has a Gitlab account. Yes it's easy to get a Gitlab account for free, but that's still a barrier at the moment.
- krzyk 6y agoThey have previously chosen mercurial which didn't won the DVCS battle, so I assume they now bet on a winning horse.
- WhyNotHugo 6y agoUhm... GitLab also uses Git, not sure what you're talking about.