I have pushed updates to the migrated repos to update various links/metadata to the new gitbox URLs, and have updated the existing website content and the scripts etc for generating new release content. I think that mostly completes things. Things seem to be working well, but let me know of any issues.
Robbie On Fri, 14 Dec 2018 at 10:06, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > > I raised https://issues.apache.org/jira/browse/INFRA-17418 yesterday > and it was actioned last night. The repos have been migrated. > > I'm starting the process of looking for any issues, updating necessary > details in the repos (updated broker-j master pom.xml as a starter), > and updating the website. > > Folks using the "git-wip-us" repositories will need to swap over to > pulling/pushing via the new locations, swapping "git-wip-us" for > "gitbox" in any existing URLs (such as in <checkout>/.git/config). > > The GitHub mirror URLs continue as before. Committers can now gain > write access by going through the process at > https://reference.apache.org/committer/github if desired though. > > Robbie > > On Thu, 13 Dec 2018 at 13:17, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > > > > Everyone who replied is agreed on migrating now, so per the original > > mail I will raise the request shortly (once this mail is archived) to > > get things under way. > > > > Robbie > > > > On Mon, 10 Dec 2018 at 16:10, Robbie Gemmell <robbie.gemm...@gmail.com> > > wrote: > > > > > > Hi Folks, > > > > > > Per the below mail sent by the ASF Infrastructure team (to dev@), our Git > > > repositories will be migrated from the original/old git-wip-us service on > > > to > > > the newer gitbox.apache.org service by February 7th. > > > > > > This is definitely happening, but we have some say over when/how it does: > > > 1. Document consensus on list and voluntarily request to move by Jan 9th. > > > 2. Wait for mandated move between Jan 9th and Feb 6th, coordinate with > > > infra > > > to proceed once it has been. > > > 3. Do nothing, ignore the mandate, and be forcibly moved on Feb 7th. > > > > > > I'm in favour of volunteering and doing it sooner than later, so to > > > that end here is my lazy consensus statement: > > > > > > Unless there is discussion here resulting in decision to delay, I will > > > raise the migration request JIRA with Infra on Thursday 13th Dec, > > > hopefully allowing completion of the process by the end of this week > > > if they have bandwidth to do so. > > > > > > Robbie > > > > > > On Fri, 7 Dec 2018 at 16:52, Daniel Gruno wrote: > > > > > > > > [NOTICE] Mandatory relocation of Apache git repositories on > > > > git-wip-us.apache.org > > > > > > > > > > > > [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE > > > > DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS] > > > > > > > > Hello Apache projects, > > > > > > > > I am writing to you because you may have git repositories on the > > > > git-wip-us server, which is slated to be decommissioned in the coming > > > > months. All repositories will be moved to the new gitbox service which > > > > includes direct write access on github as well as the standard ASF > > > > commit access via gitbox.apache.org. > > > > > > > > ## Why this move? ## > > > > The move comes as a result of retiring the git-wip service, as the > > > > hardware it runs on is longing for retirement. In lieu of this, we > > > > have decided to consolidate the two services (git-wip and gitbox), to > > > > ease the management of our repository systems and future-proof the > > > > underlying hardware. The move is fully automated, and ideally, nothing > > > > will change in your workflow other than added features and access to > > > > GitHub. > > > > > > > > ## Timeframe for relocation ## > > > > Initially, we are asking that projects voluntarily request to move > > > > their repositories to gitbox, hence this email. The voluntary > > > > timeframe is between now and January 9th 2019, during which projects > > > > are free to either move over to gitbox or stay put on git-wip. After > > > > this phase, we will be requiring the remaining projects to move within > > > > one month, after which we will move the remaining projects over. > > > > > > > > To have your project moved in this initial phase, you will need: > > > > > > > > - Consensus in the project (documented via the mailing list) > > > > - File a JIRA ticket with INFRA to voluntarily move your project repos > > > > over to gitbox (as stated, this is highly automated and will take > > > > between a minute and an hour, depending on the size and number of > > > > your repositories) > > > > > > > > To sum up the preliminary timeline; > > > > > > > > - December 9th 2018 -> January 9th 2019: Voluntary (coordinated) > > > > relocation > > > > - January 9th -> February 6th: Mandated (coordinated) relocation > > > > - February 7th: All remaining repositories are mass migrated. > > > > > > > > This timeline may change to accommodate various scenarios. > > > > > > > > ## Using GitHub with ASF repositories ## > > > > When your project has moved, you are free to use either the ASF > > > > repository system (gitbox.apache.org) OR GitHub for your development > > > > and code pushes. To be able to use GitHub, please follow the primer > > > > at: https://reference.apache.org/committer/github > > > > > > > > > > > > We appreciate your understanding of this issue, and hope that your > > > > project can coordinate voluntarily moving your repositories in a > > > > timely manner. > > > > > > > > All settings, such as commit mail targets, issue linking, PR > > > > notification schemes etc will automatically be migrated to gitbox as > > > > well. > > > > > > > > With regards, Daniel on behalf of ASF Infra. > > > > > > > > PS:For inquiries, please reply to us...@infra.apache.org, not your > > > > project's dev list :-). > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
