I've said it before and I'll say it again... It makes zero sense to centralize something that was meant to be decentralized.<p>We need issues, pull requests, comments, milestones, wiki, etc... all to be decentralized.
No reason this stuff cannot be modeled using existing Git objects.<p>GitHub, GitLab and BitBucket are extremely similar. Almost 100% overlap, you could use the lowest common denominator between the 3 and you'd still have 95% of the features.
Now that sysadmin guy who told me: "what happens when bitbucket goes down?" when I asked him to move our repos to the cloud, he is smiling. Sometimes it's best to keep stuff in your own servers, if you have any...
Great. I need to push some stuff real soon now. In the last 12 months Bitbucket had an uncomfortably high number of issues. But whenever I think about moving our company code to GitLab or GitHub I envision going into a world of pain with my eng. team.<p>Has anyone got some advice for pain-free migration to GitLab or GitHub?
Often there's no preservation of past failure states so people can see (for whatever reason) what the failure looked like. Here's what <a href="https://bitbucket.org/chromiumembedded/cef/" rel="nofollow">https://bitbucket.org/chromiumembedded/cef/</a> (a totally random repository that was in my history) looks right now: <a href="http://archive.is/g0I6O" rel="nofollow">http://archive.is/g0I6O</a>
Investigating - Following reports from customers starting at 12:45 UTC, Bitbucket Cloud became unavailable.
Our engineering team is currently investigating this issue. We will provide an update as soon as we have further information. Oct 16, 12:56 UTC
<i>" Our engineering team has identified the root cause of the issue and a fix has been applied. We are currently verifying that the incident is fully resolved. Oct 16, 13:48 UTC"</i>
If you have one of these services you should probably invest in a backup system. Either a self hosted Gitlab or even just a clone of your repositories on a server or like AWS CodeConnect .