Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Fix Version/s: May 2014
    • Component/s: Git
    • Labels:
      None

      Description

      Hi all,

      Hbase community has decided that they want to make the switch from SVN
      to Git. I hope I can outline all the necessary info here. Community
      consensus was reached on dev@hbase.apache.org with no dissents. You
      can see our Voting this link
      https://mail-archives.apache.org/mod_mbox/hbase-dev/201405.mbox/%3CCADcMMgGwL4H6A%2Bn%2B28M-QxRjW%2B0Wcx0YwBNgG2riBxR_DMZ5Jg%40mail.gmail.com%3E

      1. Transition main repo https://svn.apache.org/repos/asf/hbase/,
      renaming trunk -> master, branches as-is and tags as-is.
      2. Please make sure the new repos are mirroring properly to the ASF
      Github account and http://git.apache.org/
      2. Transition from svn2jira to git2jira
      4. Please have pull-request notifications via the ASF Github account
      sent to dev@hbase.apache.org

      Thanks for your time and please let me know if you need anything else
      to begin. CC'ing other Hbase dev/pmc to help on our end [~stack].

        Activity

        Hide
        Jake Farrell added a comment -
        Migration started, svn paths are now read only and i've added a README [1] to your base svn path.

        [1]: https://svn.apache.org/repos/asf/hbase/README
        Show
        Jake Farrell added a comment - Migration started, svn paths are now read only and i've added a README [1] to your base svn path. [1]: https://svn.apache.org/repos/asf/hbase/README
        Hide
        Talat UYARER added a comment -
        Hi [~jfarrell],

        When does migration finish ?
        Show
        Talat UYARER added a comment - Hi [~jfarrell], When does migration finish ?
        Hide
        Jake Farrell added a comment -
        hi [~talat], as of 9a est this morning the migration had processed up to r1185975 with current svn HEAD at r1596569, would expect this to finish in next couple hours. I'll post back on this ticket when its done.
        Show
        Jake Farrell added a comment - hi [~talat], as of 9a est this morning the migration had processed up to r1185975 with current svn HEAD at r1596569, would expect this to finish in next couple hours. I'll post back on this ticket when its done.
        Hide
        stack added a comment -
        [~jfarrell] A few minor items:

        Commits will still go to our commits@hbase mailing list?

        Is there anything we need to do to make stuff work on reviewboard?

        Thanks.
        Show
        stack added a comment - [~jfarrell] A few minor items: Commits will still go to our commits@hbase mailing list? Is there anything we need to do to make stuff work on reviewboard? Thanks.
        Hide
        Jake Farrell added a comment -
        hi [~stack] Yes, commit notices will still go to commits@hbase. Once the git repo is verified I can help switch reviewboard over to use the new git repository, if you have any other questions please let me know
        Show
        Jake Farrell added a comment - hi [~stack] Yes, commit notices will still go to commits@hbase . Once the git repo is verified I can help switch reviewboard over to use the new git repository, if you have any other questions please let me know
        Hide
        stack added a comment -
        [~jfarrell] Thanks boss.

        My guess is migration is not done yet? I just took a look at branches listing and a few small differences still (These are 'missing' still:

          remotes/origin/0.89.0621 0454a5a Branch for first 0.89 dev release (0.89.0621)
          remotes/origin/0.89.20100830 5359718 Preparing to tag
          remotes/origin/0.90_coprocessors f7b2c77 create branch 0.90_coprocessors for HBASE-2000 work (and subtasks)
          remotes/origin/0.92.0rc4 3090251 Tagging rc4 for 0.92.0
          remotes/origin/0.94-test 165088e now roll to r1416073
          remotes/origin/testing_remove 3735dfe [maven-release-plugin] prepare for next development iteration

        }

        Thanks.
        Show
        stack added a comment - [~jfarrell] Thanks boss. My guess is migration is not done yet? I just took a look at branches listing and a few small differences still (These are 'missing' still:   remotes/origin/0.89.0621 0454a5a Branch for first 0.89 dev release (0.89.0621)   remotes/origin/0.89.20100830 5359718 Preparing to tag   remotes/origin/0.90_coprocessors f7b2c77 create branch 0.90_coprocessors for HBASE-2000 work (and subtasks)   remotes/origin/0.92.0rc4 3090251 Tagging rc4 for 0.92.0   remotes/origin/0.94-test 165088e now roll to r1416073   remotes/origin/testing_remove 3735dfe [maven-release-plugin] prepare for next development iteration } Thanks.
        Hide
        Jake Farrell added a comment -
        hey [~stack], you can watch here [1] for it to be done and ready for verification. If you are looking at Github then this is currently a mirror of the svn code and will get cleaned up during this process.

        [1]: https://git-wip-us.apache.org/repos/asf?p=hbase.git
        Show
        Jake Farrell added a comment - hey [~stack], you can watch here [1] for it to be done and ready for verification. If you are looking at Github then this is currently a mirror of the svn code and will get cleaned up during this process. [1]: https://git-wip-us.apache.org/repos/asf?p=hbase.git
        Hide
        Andrew Purtell added a comment -
        Thanks a lot [~jfarrell]. Can you confirm that force pushes are disallowed? Is that a global policy for git-wip-us or can it be changed on a per project setting? Is there an infra wiki that could help with self service education about Apache Git hosting? Please pardon the ignorant questions.
        Show
        Andrew Purtell added a comment - Thanks a lot [~jfarrell]. Can you confirm that force pushes are disallowed? Is that a global policy for git-wip-us or can it be changed on a per project setting? Is there an infra wiki that could help with self service education about Apache Git hosting? Please pardon the ignorant questions.
        Hide
        Jake Farrell added a comment -
        Hey [~apurtell], ask away happy to answer any questions you have either in this ticket or on irc if you want to chat. Force pushes are disabled across the board as a global policy and are configured at a per project level of control, we rarely open this up and it is temporary for things like imports.
        Show
        Jake Farrell added a comment - Hey [~apurtell], ask away happy to answer any questions you have either in this ticket or on irc if you want to chat. Force pushes are disabled across the board as a global policy and are configured at a per project level of control, we rarely open this up and it is temporary for things like imports.
        Hide
        Andrew Purtell added a comment -
        Great [~jfarrell], thanks
        Show
        Andrew Purtell added a comment - Great [~jfarrell], thanks
        Hide
        Jake Farrell added a comment -
        Migration is complete, please verify [1](web) and [2](commits) and post back on this ticket. Once verified i'll remove the existing svn Github mirror and recreate them

        [1]: https://git-wip-us.apache.org/repos/asf?p=hbase.git
        [2]: https://git-wip-us.apache.org/repos/asf/hbase.git
        Show
        Jake Farrell added a comment - Migration is complete, please verify [1](web) and [2](commits) and post back on this ticket. Once verified i'll remove the existing svn Github mirror and recreate them [1]: https://git-wip-us.apache.org/repos/asf?p=hbase.git [2]: https://git-wip-us.apache.org/repos/asf/hbase.git
        Hide
        stack added a comment -
        On tags, there are some differences. We could live with the difference I'd say (can point folks at SVN if they want to go back in time). Here is a sample (about 5% difference by guestimate -- I can give a more accurate number if wanted):

        + Missing from git tags but in svn tags

        0.89.20100621-0.89.20100621-rc1
        0.89.20100726RC2

        + git tags that are not in svn as tags:

        0.95.1-hadoop1.mvnlabeling2
        0.95.1-hadoop2.mvn.label4
        0.96.1new
        0.96.2-RC2
        hbase-0.95.2-hadoop2
        hbase-0.95.1-hadoop2.by.mvn
        hbase-0.95.2-hadoop2-testing
        ...

        For branches, I notice that we have the following in GIT but not in SVN:

          remotes/origin/0.89-fb-accidentally-wiped-commit-log
        remotes/origin/0.89.20100830
          remotes/origin/0.90_coprocessors
          remotes/origin/0.92.0rc4
        ... and a few others

        Maybe they were deleted from SVN? They important ones are there so again, should be no prob. Just asking...


        #1 above asks "Transition main repo https://svn.apache.org/repos/asf/hbase/, renaming trunk -> master, branches as-is and tags as-is." It looks like we still have trunk. Thats no problem but wondering if there is a reason?



        Otherwise, commit logs look good. One of the lads tried trunk and its looking good. I tried a branch. Ditto.

        Thanks [~jfarrell]
        Show
        stack added a comment - On tags, there are some differences. We could live with the difference I'd say (can point folks at SVN if they want to go back in time). Here is a sample (about 5% difference by guestimate -- I can give a more accurate number if wanted): + Missing from git tags but in svn tags 0.89.20100621-0.89.20100621-rc1 0.89.20100726RC2 + git tags that are not in svn as tags: 0.95.1-hadoop1.mvnlabeling2 0.95.1-hadoop2.mvn.label4 0.96.1new 0.96.2-RC2 hbase-0.95.2-hadoop2 hbase-0.95.1-hadoop2.by.mvn hbase-0.95.2-hadoop2-testing ... For branches, I notice that we have the following in GIT but not in SVN:   remotes/origin/0.89-fb-accidentally-wiped-commit-log remotes/origin/0.89.20100830   remotes/origin/0.90_coprocessors   remotes/origin/0.92.0rc4 ... and a few others Maybe they were deleted from SVN? They important ones are there so again, should be no prob. Just asking... #1 above asks "Transition main repo https://svn.apache.org/repos/asf/hbase/, renaming trunk -> master, branches as-is and tags as-is." It looks like we still have trunk. Thats no problem but wondering if there is a reason? Otherwise, commit logs look good. One of the lads tried trunk and its looking good. I tried a branch. Ditto. Thanks [~jfarrell]
        Hide
        Jake Farrell added a comment -
        Hey [~stack], Are you verifying against github? trunk was renamed to master and I'm seeing both of those tags on git-wip in the import at [1] and branches at [2]. Github is still an old copy of your svn mirror and is not correct for this. I've deleted the Github mirror and setup the git.a.o mirror which Github will pickup within 24 hours. If you would like any of the github integrations enabled please create a separate ticket once the Github repo is available. If you have any questions please let me know

        0.89.20100621-0.89.20100621-rc1
        0.89.20100726RC2

        [1]: https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tags
        [2]: https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=heads
        Show
        Jake Farrell added a comment - Hey [~stack], Are you verifying against github? trunk was renamed to master and I'm seeing both of those tags on git-wip in the import at [1] and branches at [2]. Github is still an old copy of your svn mirror and is not correct for this. I've deleted the Github mirror and setup the git.a.o mirror which Github will pickup within 24 hours. If you would like any of the github integrations enabled please create a separate ticket once the Github repo is available. If you have any questions please let me know 0.89.20100621-0.89.20100621-rc1 0.89.20100726RC2 [1]: https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=tags [2]: https://git-wip-us.apache.org/repos/asf?p=hbase.git;a=heads
        Hide
        Andrew Purtell added a comment -
        I did fresh checkouts from SVN for HBase trunk and the major branches, and a fresh clone from git-wip-us.apache.org/repos/asf/hbase.git, then recursive diffs of the results excluding SCM metadata. There are differences between SVN checkouts and Git checkouts for trunk/master and the 0.98 branch. SVN has changes that did not make it over to Git looks like.

        master/trunk: http://pastebin.com/dQ6SU2Dz

        0.98: http://pastebin.com/Pvk3BH4i
        Show
        Andrew Purtell added a comment - I did fresh checkouts from SVN for HBase trunk and the major branches, and a fresh clone from git-wip-us.apache.org/repos/asf/hbase.git, then recursive diffs of the results excluding SCM metadata. There are differences between SVN checkouts and Git checkouts for trunk/master and the 0.98 branch. SVN has changes that did not make it over to Git looks like. master/trunk: http://pastebin.com/dQ6SU2Dz 0.98: http://pastebin.com/Pvk3BH4i
        Hide
        Andrew Purtell added a comment -
        Never mind, antsy committers have started on the Git repo already.
        Show
        Andrew Purtell added a comment - Never mind, antsy committers have started on the Git repo already.
        Hide
        stack added a comment -
        All looks good to me now. I must have been using a github checkout. I poked around and did compare of svn checkout and git checkout and stuff looks the same.

        Thanks [~jfarrell]
        Show
        stack added a comment - All looks good to me now. I must have been using a github checkout. I poked around and did compare of svn checkout and git checkout and stuff looks the same. Thanks [~jfarrell]
        Hide
        Hudson added a comment -
        FAILURE: Integrated in HBase-TRUNK #5137 (See [https://builds.apache.org/job/HBase-TRUNK/5137/])
        Update pom scm section to refer to apache git instead of apache svn now we migrated, INFRA-7768 (stack: rev 624e34a2a5a96b5c518376f725e9ffd5ae90227a)
        * pom.xml
        Show
        Hudson added a comment - FAILURE: Integrated in HBase-TRUNK #5137 (See [ https://builds.apache.org/job/HBase-TRUNK/5137/ ]) Update pom scm section to refer to apache git instead of apache svn now we migrated, INFRA-7768 (stack: rev 624e34a2a5a96b5c518376f725e9ffd5ae90227a) * pom.xml

          People

          • Assignee:
            Jake Farrell
            Reporter:
            Talat UYARER
          • Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development