About

About.GitHub-Migration History

Hide minor edits - Show changes to markup

November 04, 2013, at 05:46 PM by bogdan -
Changed line 1 from:

Migrating OpenSIPS to GitHub

to:
Migrating OpenSIPS to GitHub
Changed line 4 from:

Migrating to Git

to:

Migrating to Git

Changed lines 9-10 from:

Schedule

to:

Schedule

Changed line 18 from:

Resources

to:

Resources

May 20, 2013, at 07:15 PM by razvancrainea -
Changed line 9 from:
to:

Schedule

May 20, 2013, at 07:15 PM by razvancrainea -
Changed line 9 from:

Schedule

to:
May 20, 2013, at 06:27 PM by razvancrainea -
Changed lines 7-8 from:
to:
  • GitHub OpenSIPS Organization
Added line 22:
  • GitHub OpenSIPS Organization
May 20, 2013, at 06:23 PM by razvancrainea -
Changed lines 5-6 from:
to:
May 20, 2013, at 06:19 PM by razvancrainea -
Changed line 6 from:
to:
May 20, 2013, at 06:19 PM by razvancrainea -
Added lines 3-6:

Migrating to Git

May 20, 2013, at 05:52 PM by razvancrainea -
Changed line 8 from:
  • 13-17 May 2013 - Testing period (both repositories will be read-only)* Official Git Tutorial.
to:
  • 13-17 May 2013 - Testing period (both repositories will be read-only)
May 20, 2013, at 05:50 PM by razvancrainea -
Changed lines 16-17 from:
  • GitHub Migration poll results
to:
May 20, 2013, at 05:48 PM by razvancrainea -
Deleted lines 3-75:

Current repositories

During our migration process from SVN to GIT and SourceForge to GitHub, due to constraints imposed by SourceForge, we ended up with a couple of new repositories:

StatusTypeHostedURLModeDescription
Old/ObsoleteSVNSourceForgehttps://opensips.svn.sourceforge.net/svnroot/opensipsRead OnlyStarting from revision #10024 will no longer be updated/synchornized
NewSVNSourceForgehttps://svn.code.sf.net/p/opensips/svnRead OnlySynchronized with main git repository
NewGITGitHubhttps://github.com/OpenSIPS/ospensips.gitRead WriteMain repository

(:comment || New || SVN || GitHub || https://github.com/OpenSIPS/opensips || Read Only || For SVN lovers, synchronized with main git repository ||:)

Important: Since the old repository is obsolete, we strongly recommend you to migrate to one of the new repositories. The new SVN repository from SourceForge will be periodically (every 30 minutes) synchronized with the Main Git Repository. This will allow your old repositories to be further up to date.


Migration

This tutorial is addressed to the entire OpenSIPS community, both developers and users. It aims to help you migrate to one of our new repositories, depending on your preferences and needs.

I am a Read-Only User...

  • and I have an old SVN checkout and I don't want to do a fresh checkout
In order to keep your sources up-to-date we strongly recommend you to configure your SVN repository to point to the new SourceForge SVN repository. This can be achieved using the svn relocate command (or for older svn versions svn switch --relocate command).
Example: to migrate an old OpenSIPS 1.9 SVN checkout to the new SourceForge SVN repository you can use:
svn relocate https://svn.code.sf.net/p/opensips/svn/branches/1.9
or (if previous command returns Unknown command: 'relocate')
svn switch --relocate https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.9 https://svn.code.sf.net/p/opensips/svn/branches/1.9
After changing the SVN URL, you will be able to pull the updates from SourceForge in the same way you were doing until now, using the svn update command.


  • I want to do a fresh checkout, but I don't like git
You will still be able to do a SVN checkout on the new SourceForge repository. However, you should strongly consider the migration to a git repository, since on long term we are planning to move completely on GitHub, and the repository might become obsolete.
Example: if you want a fresh checkout of the 1.9 branch, you should use:
svn checkout https://svn.code.sf.net/p/opensips/svn/branches/1.9


  • and I am willing to use a fresh git clone
This is the option we recommend. If you are not that familiar with git, we recommend you to go through the official Git Manual.
Example: in order to do a new clone of the 1.9 branch, you can do:
git checkout -b 1.9 https://github.com/OpenSIPS/opensips.git opensips_1_9

I am a Developer...

Important: starting with the migration, you will no longer be able to use SVN to push changes to OpenSIPS. Since the Git versioning system is a bit different than SVN, we strongly recommend you to go through the Git Official tutorial. The following tutorial contains a few steps.
In order to commit on the new Git repository, you first have to clone it:
Example: in order to clone the 1.9 branch, you have to run:
git checkout -b 1.9 https://github.com/OpenSIPS/opensips.git opensips_1_9
Make the necessary changes and then commit them on your local repository:
Example: commit the changes on the main.c file
git add main.c
git commit -m 'Commit message for main.c modifications'
Ensure that your repository is up-to-date - fetch any changes (and also rebase).
Example: to fetch the changes from 1.9 branch of the origin repository
git pull --rebase origin 1.9
Push your changes upstream.
Example: to push the changes from the local branch to the remote 1.9 branch of the origin repository, use:
git push origin 1.9

Changed line 8 from:
  • 13-17 May 2013 - Testing period (both repositories will be read-only)
to:
  • 13-17 May 2013 - Testing period (both repositories will be read-only)* Official Git Tutorial.
Changed line 12 from:

to:
Changed lines 16-17 from:
  • GitHub Migration poll results
  • Official Git Tutorial.
to:
  • GitHub Migration poll results
May 20, 2013, at 04:41 PM by razvancrainea -
Changed lines 30-32 from:
or
svn svn switch --relocate https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.9 https://svn.code.sf.net/p/opensips/svn/branches/1.9
to:
or (if previous command returns Unknown command: 'relocate')
svn switch --relocate https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.9 https://svn.code.sf.net/p/opensips/svn/branches/1.9
Changed lines 48-49 from:
This is the option we recommend. If you are not that familiar with git, we recommend you to pass through the official Git Manual.
to:
This is the option we recommend. If you are not that familiar with git, we recommend you to go through the official Git Manual.
Changed line 55 from:
Important: starting with the migration, you will no longer be able to use SVN to push changes to OpenSIPS. Since the Git versioning system is a bit different than SVN, we strongly recommend you to pass through the Git Official tutorial. The following tutorial contains a few steps.
to:
Important: starting with the migration, you will no longer be able to use SVN to push changes to OpenSIPS. Since the Git versioning system is a bit different than SVN, we strongly recommend you to go through the Git Official tutorial. The following tutorial contains a few steps.
May 20, 2013, at 04:32 PM by razvancrainea -
Changed line 11 from:
NewGITGitHubhttps://github.com/OpenSIPS/opensips.gitRead WriteMain repository
to:
NewGITGitHubhttps://github.com/OpenSIPS/ospensips.gitRead WriteMain repository
Changed lines 51-74 from:
git checkout -b 1.9 https://github.com/OpenSIPS/opensips.git opensips_1_9
to:
git checkout -b 1.9 https://github.com/OpenSIPS/opensips.git opensips_1_9

I am a Developer...

Important: starting with the migration, you will no longer be able to use SVN to push changes to OpenSIPS. Since the Git versioning system is a bit different than SVN, we strongly recommend you to pass through the Git Official tutorial. The following tutorial contains a few steps.
In order to commit on the new Git repository, you first have to clone it:
Example: in order to clone the 1.9 branch, you have to run:
git checkout -b 1.9 https://github.com/OpenSIPS/opensips.git opensips_1_9
Make the necessary changes and then commit them on your local repository:
Example: commit the changes on the main.c file
git add main.c
git commit -m 'Commit message for main.c modifications'
Ensure that your repository is up-to-date - fetch any changes (and also rebase).
Example: to fetch the changes from 1.9 branch of the origin repository
git pull --rebase origin 1.9
Push your changes upstream.
Example: to push the changes from the local branch to the remote 1.9 branch of the origin repository, use:
git push origin 1.9
May 20, 2013, at 04:04 PM by razvancrainea -
Changed lines 12-13 from:
NewSVNGitHubhttps://github.com/OpenSIPS/opensipsRead OnlyFor SVN lovers, synchronized with main git repository
to:

(:comment || New || SVN || GitHub || https://github.com/OpenSIPS/opensips || Read Only || For SVN lovers, synchronized with main git repository ||:)

Changed lines 15-16 from:
to:

The new SVN repository from SourceForge will be periodically (every 30 minutes) synchronized with the Main Git Repository. This will allow your old repositories to be further up to date.

Changed lines 22-25 from:

I am an Read-only User and...

  • I have an old SVN checkout and I don't want to do a fresh checkout
to:

I am a Read-Only User...

  • and I have an old SVN checkout and I don't want to do a fresh checkout
Changed line 29 from:
svn relocate https://svn.code.sf.net/p/opensips/svn/branches/1.9
to:
svn relocate https://svn.code.sf.net/p/opensips/svn/branches/1.9
Changed lines 31-33 from:
svn svn switch --relocate https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.9 https://svn.code.sf.net/p/opensips/svn/branches/1.9
to:
svn svn switch --relocate https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.9 https://svn.code.sf.net/p/opensips/svn/branches/1.9
After changing the SVN URL, you will be able to pull the updates from SourceForge in the same way you were doing until now, using the svn update command.


  • I want to do a fresh checkout, but I don't like git
You will still be able to do a SVN checkout on the new SourceForge repository. However, you should strongly consider the migration to a git repository, since on long term we are planning to move completely on GitHub, and the repository might become obsolete.
Example: if you want a fresh checkout of the 1.9 branch, you should use:
svn checkout https://svn.code.sf.net/p/opensips/svn/branches/1.9


  • and I am willing to use a fresh git clone
This is the option we recommend. If you are not that familiar with git, we recommend you to pass through the official Git Manual.
Example: in order to do a new clone of the 1.9 branch, you can do:
git checkout -b 1.9 https://github.com/OpenSIPS/opensips.git opensips_1_9
Changed lines 66-67 from:
  • GitHub Migration poll results
to:
  • GitHub Migration poll results
  • Official Git Tutorial.
May 20, 2013, at 02:21 PM by razvancrainea -
Changed lines 23-33 from:
  1. I have an old SVN checkout and I don't want to do a fresh checkout

In order to keep your sources up-to-date we strongly recommend you to configure your SVN repository to point to the new SourceForge SVN repository. This can be achieved using the svn relocate command (or for older svn versions svn switch --relocate command).

Example: to migrate an old OpenSIPS 1.9 SVN checkout to the new SourceForge SVN repository you can use:

   # svn relocate https://svn.code.sf.net/p/opensips/svn/branches/1.9 #

or

   # svn svn switch --relocate https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.9 https://svn.code.sf.net/p/opensips/svn/branches/1.9 #
to:
  • I have an old SVN checkout and I don't want to do a fresh checkout
In order to keep your sources up-to-date we strongly recommend you to configure your SVN repository to point to the new SourceForge SVN repository. This can be achieved using the svn relocate command (or for older svn versions svn switch --relocate command).
Example: to migrate an old OpenSIPS 1.9 SVN checkout to the new SourceForge SVN repository you can use:
svn relocate https://svn.code.sf.net/p/opensips/svn/branches/1.9
or
svn svn switch --relocate https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.9 https://svn.code.sf.net/p/opensips/svn/branches/1.9
May 20, 2013, at 02:14 PM by razvancrainea -
Changed lines 4-5 from:

Schedule

to:

Current repositories

During our migration process from SVN to GIT and SourceForge to GitHub, due to constraints imposed by SourceForge, we ended up with a couple of new repositories:

StatusTypeHostedURLModeDescription
Old/ObsoleteSVNSourceForgehttps://opensips.svn.sourceforge.net/svnroot/opensipsRead OnlyStarting from revision #10024 will no longer be updated/synchornized
NewSVNSourceForgehttps://svn.code.sf.net/p/opensips/svnRead OnlySynchronized with main git repository
NewGITGitHubhttps://github.com/OpenSIPS/opensips.gitRead WriteMain repository
NewSVNGitHubhttps://github.com/OpenSIPS/opensipsRead OnlyFor SVN lovers, synchronized with main git repository

Important: Since the old repository is obsolete, we strongly recommend you to migrate to one of the new repositories.


Migration

This tutorial is addressed to the entire OpenSIPS community, both developers and users. It aims to help you migrate to one of our new repositories, depending on your preferences and needs.

I am an Read-only User and...

  1. I have an old SVN checkout and I don't want to do a fresh checkout

In order to keep your sources up-to-date we strongly recommend you to configure your SVN repository to point to the new SourceForge SVN repository. This can be achieved using the svn relocate command (or for older svn versions svn switch --relocate command).

Example: to migrate an old OpenSIPS 1.9 SVN checkout to the new SourceForge SVN repository you can use:

   # svn relocate https://svn.code.sf.net/p/opensips/svn/branches/1.9 #

or

   # svn svn switch --relocate https://opensips.svn.sourceforge.net/svnroot/opensips/branches/1.9 https://svn.code.sf.net/p/opensips/svn/branches/1.9 #

Schedule

Changed lines 45-46 from:

Resources

to:

Resources

April 25, 2013, at 11:26 AM by razvancrainea -
April 25, 2013, at 11:25 AM by razvancrainea -
Changed lines 9-10 from:
  • 20 May 2013 - Final release
to:
  • 20 May 2013 - Git repository final release
  • 20-24 May 2013 - Moving the tracker (bugs, patches, etc) from SourceForge to GitHub
April 25, 2013, at 10:11 AM by razvancrainea -
Added lines 1-14:

Migrating OpenSIPS to GitHub


Schedule

  • 8 May 2013 - Freeze SourceForge SVN Repository
  • 9-10 May 2013 - Migrating the entire OpenSIPS repository to GitHub
  • 13-17 May 2013 - Testing period (both repositories will be read-only)
  • 20 May 2013 - Final release

Resources

  • GitHub website
  • GitHub Migration poll results

Page last modified on November 04, 2013, at 05:46 PM