Re: [naviserver-devel] Mercurial at Bitbucket is ending. What next?

[Gustaf N. <ne...@wu...>]

Dear all,

Bitbucket has defined the following dates for shutting down their
mercurial support, which are in the not too distant future:

  - February 1, 2020: users will no longer be able to create new 
Mercurial repositories
  - June 1, 2020: users will not be able to use Mercurial features in
     Bitbucket or via its API and all Mercurial repositories will be 
removed.
  - All current Mercurial functionality in Bitbucket will be available 
through May 31, 2020.

These dates are approaching quickly. I fully agree with Zoran about git,
although there are as well merits in other systems. Keep in mind that we
have more than 70 naviserver+modules repositories, and we have to
carry the accounts and permissions to some target system.

 From the effort point of view, a migration from bitbucket+hg to 
bitbucket+git
would be my preferred way, in case, i am doing the conversions. So please
speak up now, if someone objects.

As a proof of concept, i've transformed two repositories to
bitbucket+git by adding a "-git" suffix to the repository name:

    https://bitbucket.org/naviserver/naviserver-git

I would be glad, if some of our developers with git experience
can checkout  this git repo of naviserver to see, whether this
looks ok to you. In the future, we should change from a tagging
model to a branching model, but currently this is just a 1:1 conversion.

Once we are convinced this is fine, then we can do the same on all 70+
other repos, and make some tests to check, if everything looks fine.
Then in the last step do a final renaming game
to swap to the original repository names:

   1) rename hg-repo from NAME to NAME-hg
   2) rename git-repo from NAME-git to NAME
   3) set hg repo to READ-only

... and certainly change the documentation/READMEs
from hg to git.

... please do not commit to the git repo, continue to
commit to hg for the time being. Part of the conversion has
to be done manually (creating the repos, renaming the repos,
transferring individual permissions), part can be done scripted.

all the best

-gn

On 29.08.19 12:06, Zoran Vasiljevic wrote:
> On Thu, 29 Aug 2019 09:13:17 +0000 (UTC)
> Roderick <hr...@gm...> wrote:
>
>> After reading something about mercurial only for cloning Naviservers
>> Repo, I read this:
>>
>> https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket
>>
>> It would be nice to have NaviServer as fossil repo. :)
> I believe most logical choice is git. I'm not fan of any of
> the systems, to be honest. Just, the chance that we will have
> to switch again (cvs -> mercurial -> ?) is less if the ? = git.