+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 <robbie.gemm...@gmail.com> 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 <oru...@gmail.com> 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 <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
> > >
> >
> > ---------------------------------------------------------------------
> > 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
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Reply via email to