From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============8020675865237073700==" MIME-Version: 1.0 From: Howell, Seth Subject: [SPDK] Re: New Gerrit Instance Date: Tue, 04 Feb 2020 16:35:07 +0000 Message-ID: In-Reply-To: EA913ED399BBA34AA4EAC2EDC24CDD00CD73996F@FMSMSX105.amr.corp.intel.com List-ID: To: spdk@lists.01.org --===============8020675865237073700== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi All, I want to clarify the statement: "as of tomorrow, all of your open changes = will need to be re-uploaded to review.spdk.io". By that I mean that the mai= ntainers will be merging pre-existing changes from review.gerrithub.io unti= l about 12:00 AM GMT on 2/5/2020. Any new changes you make from now on shou= ld be submitted directly to review.spdk.io, and any changes left on review.= gerrithub.io after 12:00 AM GMT on 2/5/2020 should be re-submitted to revie= w.spdk.io. Thank you, Seth Howell -----Original Message----- From: Howell, Seth = Sent: Tuesday, February 4, 2020 8:42 AM To: Storage Performance Development Kit Subject: [SPDK] New Gerrit Instance Hi all, With a successful 20.01 release behind us, we are excited to announce a cha= nge to the SPDK CI system that will help our project remain independent, an= d ensure the reliability of the CI infrastructure. We are migrating our rev= iew services from review.gerrithub.io to a new, community hosted domain, re= view.spdk.io. What does this mean for you as a developer? The change to your day to day operations should be small. The initial work = is also quite simple: 1. Navigate to review.spdk.io and login using the login button in the to= p right. We use GitHub OAUTH the same as review.gerrithub.io 2. Upload any public ssh keys you use to upload to GerritHub to the new = site under the settings tab and generate an https password if desired. The = https://spdk.io/development/#gerrithub guide can be useful here as the step= s are the same. 3. All of the repositories in review.spdk.io have the same names as thei= r review.spdk.io equivalents, and all of the refs/for paths are equivalent.= This means that you can simply go into your existing local spdk/* GitHub r= epositories, update all remote references from review.gerrithub.io to revie= w.spdk.io in your .git/config file and continue using the same repository f= or review.spdk.io 4. As of tomorrow, all of your open changes will need to be re-uploaded = to review.spdk.io. If you performed step 3, you can simply checkout the lat= est master, rebase your local branches on top of that, and push to the prop= er review branch (whatever names you have configured in your local .git/con= fig file). All of the spdk/* projects currently in review.gerrithub.io have been copie= d over to review.spdk.io so you should be able to resume development on any= of those projects immediately after the switch. Karol Latecki and myself w= ill both be available to answer questions in real time in the days followin= g the transition on the SPDK Jenkins-ci and general slack channels. All other features of Gerrit will remain the same. Links to logs will be po= sted automatically to the reviews as they complete, and -1 tags can be remo= ved using the false positive reporting system. If you encounter any issues = with review.spdk.io, please reach out on the SPDK slack channel. Here's looking forward to a great 2020 and the continued growth of the SPDK= development community! Thank you, Seth Howell Summary: The new Gerrit server is located at review.spdk.io. Please migrate= your patches to that server starting tomorrow. _______________________________________________ SPDK mailing list -- spdk(a)lists.01.org To unsubscribe send an email to spdk-leave(a)lists.01.org --===============8020675865237073700==--