Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
I noticed just now that the GitHub PR integration behaviour had changed since the migration, with comments not being left on the JIRA for PR open/close/comments etc, but rather 10minute time-spent entries made to the Work Log instead to carry activity from the PR. I asked infra about it and theyve updated the settings to use the comments as before. I found the Work Log version surprising and not as nice, but if anyone is particularly fond of the alternative method we can discuss moving to it separately on a new thread. Robbie On Sat, 15 Dec 2018 at 18:35, Robbie Gemmell wrote: > > As you've noticed before hitting send on your mail, I had asked on the > JIRA about this already and was told the old links will be fixed by a > DNS CNAME addition once all repositories have eventually migrated. I > guess this will be as part of the ultimate 'forced migration' on Feb > 7th, unless they have actually all been migrated before then. > > Note that until that happens the adjustment needed for any old links > like below is just changing the "git-wip-us" subdomain in the URL to > "gitbox" since both are using the same web ui, just using different > versions. > > Robbie > > On Sat, 15 Dec 2018 at 15:52, Jiri Daněk wrote: > > > > Never mind, comment on the migration Jira says that the link redirect will > > be taken care of! Awesome. > > > > On Mon, Dec 10, 2018 at 5:10 PM Robbie Gemmell > > wrote: > > [...] > > > > > 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. > > > > > [...] > > > > This broke old links in the automatic Apache Jira comments by > > https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jira-bot with > > links to related commits. See e.g. those on > > https://issues.apache.org/jira/browse/PROTON-1979. > > > > It seems that a broken link in the form of > > > > https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5ba471d > > > > can be rewritten to a working link > > > > https://gitbox.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=5ba471d > > > > I doubt that the migration will include fixing all the jira comments for > > outdated links, though. Or introducing redirect from the old url. > > -- > > Mit freundlichen Grüßen / Kind regards > > Jiri Daněk - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
As you've noticed before hitting send on your mail, I had asked on the JIRA about this already and was told the old links will be fixed by a DNS CNAME addition once all repositories have eventually migrated. I guess this will be as part of the ultimate 'forced migration' on Feb 7th, unless they have actually all been migrated before then. Note that until that happens the adjustment needed for any old links like below is just changing the "git-wip-us" subdomain in the URL to "gitbox" since both are using the same web ui, just using different versions. Robbie On Sat, 15 Dec 2018 at 15:52, Jiri Daněk wrote: > > Never mind, comment on the migration Jira says that the link redirect will > be taken care of! Awesome. > > On Mon, Dec 10, 2018 at 5:10 PM Robbie Gemmell > wrote: > [...] > > > 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. > > > [...] > > This broke old links in the automatic Apache Jira comments by > https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jira-bot with > links to related commits. See e.g. those on > https://issues.apache.org/jira/browse/PROTON-1979. > > It seems that a broken link in the form of > > https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5ba471d > > can be rewritten to a working link > > https://gitbox.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=5ba471d > > I doubt that the migration will include fixing all the jira comments for > outdated links, though. Or introducing redirect from the old url. > -- > Mit freundlichen Grüßen / Kind regards > Jiri Daněk - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
Never mind, comment on the migration Jira says that the link redirect will be taken care of! Awesome. On Mon, Dec 10, 2018 at 5:10 PM Robbie Gemmell wrote: [...] > 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. > [...] This broke old links in the automatic Apache Jira comments by https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jira-bot with links to related commits. See e.g. those on https://issues.apache.org/jira/browse/PROTON-1979. It seems that a broken link in the form of https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5ba471d can be rewritten to a working link https://gitbox.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=5ba471d I doubt that the migration will include fixing all the jira comments for outdated links, though. Or introducing redirect from the old url. -- Mit freundlichen Grüßen / Kind regards Jiri Daněk
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
On 14/12/18 13:11, Robbie Gemmell wrote: 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. Thanks Robbie, all your hard for work for the project is really appreciated! - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
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 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 /.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 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 > > 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 GitHu
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
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 /.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 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 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 w
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
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 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
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
+1 to migrate asap. -Chuck - Original Message - > From: "Robbie Gemmell" > To: users@qpid.apache.org, d...@qpid.apache.org > Sent: Monday, December 10, 2018 11:10:10 AM > Subject: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org > > 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 > > - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
Great! On Mon, 10 Dec 2018 at 18:15, Oleksandr Rudyy wrote: > > +1 for early migration. > > Robbie, thanks for the detailed reply. Let's do migration first. > > Kind Regards, > Alex > On Mon, 10 Dec 2018 at 18:08, Robbie Gemmell wrote: > > > > I am volunteering, but note I'm not expecting there is much to do with > > the actual migration, just update links etc after. All that it > > constitutes is someone (me) raising the request JIRA, and waiting for > > infra to coordinate on their doing the magic (the migration is > > automated). Then there is followup bits like updating info in the poms > > and the website etc once its done, and committers obviously need to > > start pushing to a new repo location. > > > > Looking at JIRAs for existing migrations it seems swift, with one was > > done within a few hours (during which certain folks were probably > > still asleep) of the request being raised, with the actual migration > > being done inbetween 2 comments made 2 minutes apart, so I dont expect > > it to take long once underway. > > > > On the 7.1.0 release, if by the end of the week for RC1 you mean > > Friday, then I think it likely we can migrate first without holding > > that up. Even if there were a small holdup I am actually inclined to > > say we should still migrate first; 7.1.0 has been a long time coming, > > and it would be nice for its metadata etc at release to reflect the > > location the code repo will actually still be in immediately after > > that point. Any small wait (which I again dont expect will be > > necessary) to ensure the accurate info seems reasonable against the > > preceding dev period itself. > > > > Robbie > > > > On Mon, 10 Dec 2018 at 17:17, Oleksandr Rudyy wrote: > > > > > > Robbie, > > > > > > Are you volunteering to migrate all qpid git repos? I can help you > > > with migration of qpid-broker-j and legacy jms repos. > > > What is your timeline for migration? > > > > > > The reason I am asking is that I was going to cut 7.1.x branch for > > > qpid-broker-j and even produce 7.1.0 RC1 by the end of the week with a > > > hope to have it released next week :) > > > Thus, I would prefer to complete the release of 7.1.0 before the > > > migration. > > > > > > Kind Regards, > > > Alex > > > > > > > > > On Mon, 10 Dec 2018 at 16:10, Robbie Gemmell > > > 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
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
+1 for early migration. Robbie, thanks for the detailed reply. Let's do migration first. Kind Regards, Alex On Mon, 10 Dec 2018 at 18:08, Robbie Gemmell wrote: > > I am volunteering, but note I'm not expecting there is much to do with > the actual migration, just update links etc after. All that it > constitutes is someone (me) raising the request JIRA, and waiting for > infra to coordinate on their doing the magic (the migration is > automated). Then there is followup bits like updating info in the poms > and the website etc once its done, and committers obviously need to > start pushing to a new repo location. > > Looking at JIRAs for existing migrations it seems swift, with one was > done within a few hours (during which certain folks were probably > still asleep) of the request being raised, with the actual migration > being done inbetween 2 comments made 2 minutes apart, so I dont expect > it to take long once underway. > > On the 7.1.0 release, if by the end of the week for RC1 you mean > Friday, then I think it likely we can migrate first without holding > that up. Even if there were a small holdup I am actually inclined to > say we should still migrate first; 7.1.0 has been a long time coming, > and it would be nice for its metadata etc at release to reflect the > location the code repo will actually still be in immediately after > that point. Any small wait (which I again dont expect will be > necessary) to ensure the accurate info seems reasonable against the > preceding dev period itself. > > Robbie > > On Mon, 10 Dec 2018 at 17:17, Oleksandr Rudyy wrote: > > > > Robbie, > > > > Are you volunteering to migrate all qpid git repos? I can help you > > with migration of qpid-broker-j and legacy jms repos. > > What is your timeline for migration? > > > > The reason I am asking is that I was going to cut 7.1.x branch for > > qpid-broker-j and even produce 7.1.0 RC1 by the end of the week with a > > hope to have it released next week :) > > Thus, I would prefer to complete the release of 7.1.0 before the migration. > > > > Kind Regards, > > Alex > > > > > > On Mon, 10 Dec 2018 at 16:10, Robbie Gemmell > > 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
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
I am volunteering, but note I'm not expecting there is much to do with the actual migration, just update links etc after. All that it constitutes is someone (me) raising the request JIRA, and waiting for infra to coordinate on their doing the magic (the migration is automated). Then there is followup bits like updating info in the poms and the website etc once its done, and committers obviously need to start pushing to a new repo location. Looking at JIRAs for existing migrations it seems swift, with one was done within a few hours (during which certain folks were probably still asleep) of the request being raised, with the actual migration being done inbetween 2 comments made 2 minutes apart, so I dont expect it to take long once underway. On the 7.1.0 release, if by the end of the week for RC1 you mean Friday, then I think it likely we can migrate first without holding that up. Even if there were a small holdup I am actually inclined to say we should still migrate first; 7.1.0 has been a long time coming, and it would be nice for its metadata etc at release to reflect the location the code repo will actually still be in immediately after that point. Any small wait (which I again dont expect will be necessary) to ensure the accurate info seems reasonable against the preceding dev period itself. Robbie On Mon, 10 Dec 2018 at 17:17, Oleksandr Rudyy wrote: > > Robbie, > > Are you volunteering to migrate all qpid git repos? I can help you > with migration of qpid-broker-j and legacy jms repos. > What is your timeline for migration? > > The reason I am asking is that I was going to cut 7.1.x branch for > qpid-broker-j and even produce 7.1.0 RC1 by the end of the week with a > hope to have it released next week :) > Thus, I would prefer to complete the release of 7.1.0 before the migration. > > Kind Regards, > Alex > > > On Mon, 10 Dec 2018 at 16:10, Robbie Gemmell 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
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
+1 from me for early migration too, albeit from my not-so-lofty status as a very occasional committer :) On Mon, 10 Dec 2018 at 16:10, Robbie Gemmell 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: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > >
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
Robbie, Are you volunteering to migrate all qpid git repos? I can help you with migration of qpid-broker-j and legacy jms repos. What is your timeline for migration? The reason I am asking is that I was going to cut 7.1.x branch for qpid-broker-j and even produce 7.1.0 RC1 by the end of the week with a hope to have it released next week :) Thus, I would prefer to complete the release of 7.1.0 before the migration. Kind Regards, Alex On Mon, 10 Dec 2018 at 16:10, Robbie Gemmell 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 > - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
On Mon, 10 Dec 2018 at 17:10, Robbie Gemmell 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 > Not that it is required for a lazy consensus, but I am +1 on "sooner" :) -- Rob > > 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: dev-unsubscr...@qpid.apache.org > For additional commands, e-mail: dev-h...@qpid.apache.org > >
Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
On 10/12/18 16:12, Steve Huston wrote: +1 - thanks for engaging this, Robbie. +1 on all points! - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
RE: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
+1 - thanks for engaging this, Robbie. > -Original Message- > From: Robbie Gemmell > Sent: Monday, December 10, 2018 11:10 AM > To: users@qpid.apache.org; d...@qpid.apache.org > Subject: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org > > 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
