Couchbase master code fails with fatal error

I have been trying to download the master branch code and as per the github page comments used “released/elsa.xml” for it. I am getting below error for this command :

: ~/Meghali/couchbase# ./repo init -u git://github.com/couchbase/manifest.git -m released/elsa.xml
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
remote: Finding sources: 100% (7/7)
remote: Total 7 (delta 1), reused 7 (delta 1)
Unpacking objects: 100% (7/7), done.
From https://gerrit.googlesource.com/git-repo
788e962…f46902a master -> origin/master
Get https://github.com/couchbase/manifest.git
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- 0:00:01 --:–:-- 0
curl: (22) The requested URL returned error: 404 Not Found
Server does not provide clone.bundle; ignoring.
remote: Counting objects: 10869, done.
remote: Compressing objects: 100% (44/44), done.
remote: Total 10869 (delta 26), reused 34 (delta 10), pack-reused 10815
Receiving objects: 100% (10869/10869), 2.20 MiB | 1.01 MiB/s, done.
Resolving deltas: 100% (7681/7681), done.
From https://github.com/couchbase/manifest

  • [new branch] branch-171 -> origin/branch-171
  • [new branch] for-master -> origin/for-master
  • [new branch] master -> origin/master
  • [new branch] sherlock-4.0.0 -> origin/sherlock-4.0.0
  • [new branch] sherlock-4.1.0 -> origin/sherlock-4.1.0
  • [new branch] sherlock-beta -> origin/sherlock-beta
  • [new tag] 1.7.0 -> 1.7.0
  • [new tag] 1.7.0r -> 1.7.0r
  • [new tag] 1.7.1 -> 1.7.1
  • [new tag] 1.7.1.1 -> 1.7.1.1
    fatal: manifest ‘released/elsa.xml’ not available
    fatal: remote erlang not defined in /root/Meghali/couchbase/.repo/manifests/released/elsa.xml

Has anyone faced this issue recently? Am I missing anything here?
Thanks,
Meghali

Not sure what release elsa corresponds to. Suggest you follow the instructions at: https://github.com/couchbase/tlm

Thanks @drigby, for the reply!
For a specific released-branch we have xml files at released/ folder path also I read it somewhere that “elsa.xml” is being used for master-branch. Though I lost that document link.

However I will follow the link you mentioned above and see if that works for me.