Hello,
an update on this topic: the gitweb was deployed and the read-only cloning from kamailio.org mirror repository is ready. Therefore I plan to point git.sip-router.org to it on Monday, Dec 15, around noon (GMT).
I will send a notification before the procedure is started and another one when it is finished. No commit should be pushed in between (no matter what branch). After that, new commits must be pushed to github.
As an user that cloned from git.sip-router.org, pulling/fetching for updates should just work afterwards.
As a developer, you must change the remote URL (or make a new clone from github). If you are currently a developer with write access to git.sip-router.org repository and you haven't sent yet the github user id, do it as soon as possible, specially if you have commits to do in the near future.
Cheers, Daniel
On 08/12/14 09:44, Daniel-Constantin Mierla wrote:
Hello,
I setup the mirror of Kamailio github repository to kamailio.org, can be seen online at:
Mirroring is triggered by a push to github, so it is pretty much in real time.
Right now the commit and mirroring flow is:
- commit to git.sip-router.org triggers mirroring (push) to github,
which triggers a mirroring (fetch) on git.kamailio.org
Practically with a commit pushed directly to github, the first part of the above is skipped.
All seems to be ok, my last commits were done to test the mirroring including the notification emails - I will send a separate message about what we can get there.
The missing parts are the deployment of gitweb in order to have the links from archived email notifications still valid and pointing git.sip-router.org to kamailio mirror server.
Considering all above, I propose to stop committing to git.sip-router.org and pushing to github starting either next Monday (Dec 15) (or Wednesday (Dec 17) if not ready by Monday). Existing developers have to send me the github username to add it to kamailio project.
Any suggestions and comments are welcome!
Cheers, Daniel