OpenJDK (Java) migrating from Mercurial?

Sat Nov 16 20:12:29 UTC 2019

I did a little searching on this one and fond the following:

https://openjdk.java.net/jeps/357

Their official reasoning is:

Motivation
There are three primary reasons for migrating to Git:

Size of version control system metadata
Available tooling
Available hosting

Initial prototypes of converted repositories show a significant reduction
in the size of the version control metadata. For example, the .git
directory of the jdk/jdk repository is approximately 300 MB with Git and
the .hg directory is around 1.2 GB with Mercurial, depending on the
Mercurial version being used. The reduction in metadata preserves local
disk space and reduces clone times, since fewer bits have to go over the
wire. Git also features shallow clones that only clone parts of the
history, resulting in even less metadata for those users who do not need
the entire history.

There are many more tools for interacting with Git than Mercurial:

All text editors have Git integration, either natively or in the form of
plugins including Emacs (magit plugin), Vim (fugitive.git plugin), VS Code
(builtin), and Atom (builtin).

Almost all integrated development environments (IDEs) also ship with Git
integration out-of-the-box, including IntelliJ (builtin), Eclipse
(builtin), NetBeans (builtin), and Visual Studio (builtin).

There are multiple desktop clients available for interacting with Git
repositories locally.

Lastly, there are many options available for hosting Git repositories,
whether self-hosted or hosted as a service.

On Sat, Nov 16, 2019 at 9:22 AM Craig Ozancin <c.ozancin at gmail.com> wrote:

>
> On Fri, Nov 15, 2019 at 9:10 PM Scott Palmer <swpalmer at gmail.com> wrote:
>
>>
>>
>> On Nov 15, 2019, at 6:19 PM, František Kučera <konference at frantovo.cz>
>> wrote:
>>
>> Dne 26. 07. 19 v 17:19 duvall at comfychair.org napsal(a):
>>
>> On Fri, Jul 26, 2019 at 03:03:12PM +0200, Arne Babenhauserheide wrote:
>>
>> Marek Lukáš via Mercurial <mercurial at mercurial-scm.org> writes:
>> …
>> From this:
>> https://mail.openjdk.java.net/pipermail/discuss/2019-July/005096.html
>> …
>> It looks like most of the arguments for the move are not based in
>> delivering improvements with the minimal amount of breakage, but rather
>> in moving to git at any cost.
>>
>> It seems likely that's the case: some unrelated team at Oracle has made
>> the
>> decision that everything will be git, and now engineering teams (willing
>> or not)
>> have to implement that decision, regardless of external consumers.  With
>> Oracle,
>> if you're not a paying customer, you're not valued very much, if at all.
>> And
>> I'm sure that Oracle (again, as a company, not the individual teams and
>> people
>> who interact with external communities) feels that they own OpenJDK as
>> much as
>> they own Java, and that the community participation in governance is
>> simply an
>> impediment to them doing whatever they feel they need to do.
>>
>> There was strong pressure when I was still there to move the Solaris
>> repos to
>> git.  In fact, the default stance (dictated by some small team way up in
>> the
>> CTO's office, I think) was git for any external participation.  You were
>> expected to have a repo on github, though they relented and allowed us to
>> set up a mirror of the internal mercurial repo (for our opensource
>> bits).  At
>> least one other repo gave up and converted.  I wouldn't be surprised if
>> more
>> did.
>>
>> Danek
>>
>> I remember when i first heard this story, I was shocked that the reason
> the project lead
> gave for moving to git from mercurial was that out-of-the-box git had more
> available
> commands than mercurial. I seriously doubt that this guy was so stupid to
> think that was
> remotely a reasonable evaluation. Any experienced developer would spend a
> good
> amount of time doing side-by-side comparison to see which tool gives your
> the best
> performance, options and user experience. There had to be some other
> political
> reason behind the scenes.
>
>> BTW: there is a new discussion „New candidate JEP: 369: Migrate to
>> GitHub“ in the OpenJDK mailing list:
>> <
>> https://mail.openjdk.java.net/pipermail/discuss/2019-November/thread.html
>> >
>>
>> Some comments:
>>
>> I think we really need to get back to this proposal in an year or two
>> when we understand more of the implication
>>
>>
>> <
>> https://mail.openjdk.java.net/pipermail/discuss/2019-November/005200.html
>> >
>>
>> It worries me a little that an entire DVCS swap is being proposed
>> without, apparently, any attempts to speed up Mercurial operations
>> having being tried
>>
>>
>> <
>> https://mail.openjdk.java.net/pipermail/discuss/2019-November/005195.html
>> >
>>
>> Franta
>>
>>
>> Yes, but I expect it is a done deal regardless.  The discussion smells
>> like it’s just there to show they asked for input, but the decision was
>> finished long ago.  OpenJFX already moved to Git. ( I had to deal with Git
>> insanity when I submitted patches.  Such an awkward system to work with
>> when you are used to Mercurial. It was painful.)
>> They do have a lot of automation based on GitHub though.  I’ll give them
>> points for that.
>>
>> Scott
>>
>>
>> _______________________________________________
>> Mercurial mailing list
>> Mercurial at mercurial-scm.org
>> https://www.mercurial-scm.org/mailman/listinfo/mercurial
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20191116/011a103a/attachment-0002.html>