|Re: [eigen] Bitbucket is dropping its Mercurial support!|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] Bitbucket is dropping its Mercurial support!
- From: Edward Lam <edward@xxxxxxxxxx>
- Date: Wed, 21 Aug 2019 10:33:38 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sidefx.com; s=google; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=jTNSW+ECnFq+zFC0L4OseGpyrenO210CsMhuuAne2CU=; b=cv9XCwjV3nOkUcCbJCSWlZWeXfUJEUMLHrCNc61swY4IfV0UE/SO1xYOBoxX9jNNUB v7tjemlI7ww9+tQaiuUfKDAqlB1AhNG8iLn+RSJeJNlFboGT+/9/EGGXKfXepcMsP0gx e/+dWa+0hN2OZKznGoAU3DpWWWXJSzMRJZgyRlpaicqLmjBWXvpK4awemQbUR5lkeKLV ly63m0CLIPDauchae7EtHaG5Zl4qGGohvl4fL5FPYfdYQUwkNaxN0d9YIAG22zb09zCd o7RaGaaArsGtAUnlsJ5ct+KbDNozbLuwnirQyC+stp7boIBzzkMD81bXHbDFAy3BtPkO RU8w==
I find it odd that Eigen's repo isn't hosted on tuxfamily.org itself
given that https://www.mercurial-scm.org/wiki/MercurialHosting lists it
as one of the free providers.
On 8/21/2019 9:53 AM, Christoph Hertzberg wrote:
Hello Eigen users and contributers!
As some may have noticed, bitbucket/atlassian is "sunsetting" its
If they stick to their timeline, we will have to migrate until June 1st,
2020. That means we still have time, but if we do nothing, things will
Converting the repository itself to git should not be a bigger issue --
and if we do this we could as well migrate to a more mainstream provider
I think the main problems for migration are:
a) Migrating open pull-requests (for historical reasons, the
closed/merged ones should probably be archived as well)
b) Fixing internal links inside commit messages ("grafted from ...",
"fixes error introduced in commit ...")
c) Fixing external links to the repository. Most notably, any links
from our bugtracker will eventually fail (even if we stayed with
bitbucket, the hashes won't match). I doubt that we could set up any
automatic forwarding for that.
d) Any third-party which relies on our main repository will need to
change as well (not directly "our" problem, but we need to give a
reasonable amount of time for everyone to migrate to whatever will be
our future official repository).
Smaller issues (relatively easy to fix or not as important):
e) Change links from our wiki (to downloads)
f) Change URLs for automated doxygen generation and for unit-tests
g) Automatic links from the repository to our bugtracker (currently
"Bug X" automatically links to
h) Change hashes in bench/perf_monitoring/changesets.txt
I probably missed a few things ...
I see essentially three options:
1. Migrate to another mercurial provider
2. Convert to git, stay at bitbucket
3. Convert to git, migrate to another provider
Honestly, I see no good reason for option 2. And the only real reason I
see for option 1 would be that it safes a lot of hassle with b) and h)
-- also perhaps it would simplify c) (e.g., we could easily crawl
through our bugzilla-database and just replace some URLs).
Any opinions on this? Preferences for how to proceed, or other
Does anyone have experience with migrating from hg to git? Or migrating
between providers? Especially, also dealing with the issues listed above.
Does anyone see issues I forgot?