Re:Sunsetting Mercurial Support in Bitbucket
by marcosdumay on Tuesday August 20, 2019 @03:08PM
(#20750766)
I can live with the locking behavior, but VSS had a tendency of corrupting the entire repo ever few weeks that is hard to accept.
[ Parent
| on HN ]
Re:Sunsetting Mercurial Support in Bitbucket
by flukus on Tuesday August 20, 2019 @09:35PM
(#20753913)
I could live with the locking or the corrupted repos if it was half decent at just sharing code, but daily we had problems where someone would check in code, VSS would say it was checked in but the person updating would get stale versions. Sometimes if you looked at the server version it be be correct but not what you would receive on a fresh checkout.
It was literally less functional than copying to a shared drive. Of course management and other developers refused to believe that OSS solutions were better, MS ecosystem developers were an extremely insular group.
Re:Sunsetting Mercurial Support in Bitbucket
by marcosdumay on Wednesday August 21, 2019 @11:40AM
(#20758251)
Yes, there was that too. I've seen quite a few regressions caused by this.