[NOTICE] Mandatory migration of git repositories to gitbox.apache.org

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Apache Infrastructure Team
Hello, flex folks.
As stated earlier in 2018, all git repositories must be migrated from
the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
is being decommissioned. Your project is receiving this email because
you still have repositories on git-wip-us that needs to be migrated.

The following repositories on git-wip-us belong to your project:
 - flex-tlf.git
 - flex-whiteboard.git
 - flex-utilities.git
 - flex-flexunit.git
 - flex-site.git
 - flex-external.git
 - flex-sdk.git
 - flex-asjs.git
 - flex-tourjs.git
 - flex-blazeds.git
 - flex-typedefs.git
 - flex-falcon.git
 - flex-examples.git
 - flex-radii8.git


We are now entering the mandated (coordinated) move stage of the roadmap,
and you are asked to please coordinate migration with the Apache
Infrastructure Team before February 7th. All repositories not migrated
on February 7th will be mass migrated without warning, and we'd appreciate
it if we could work together to avoid a big mess that day :-).

Moving to gitbox means you will get full write access on GitHub as well,
and be able to close/merge pull requests and much more.

To have your repositories moved, please follow these steps:

- Ensure consensus on the move (a link to a lists.apache.org thread will
  suffice for us as evidence).
- Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA

Your migration should only take a few minutes. If you wish to migrate
at a specific time of day or date, please do let us know in the ticket.

As always, we appreciate your understanding and patience as we move
things around and work to provide better services and features for
the Apache Family.

Should you wish to contact us with feedback or questions, please do so
at: [hidden email].


With regards,
Apache Infrastructure

Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Olaf Krueger
Hi guys,
if I understand it correctly we have to vote for the migration and we
optionally can specify a date for it.

However,
- Does anybody know if this migration will break anything?
- Do we need to keep the FlexJS repositories (Maybe they can be deleted
because they moved to Royale)?

Thanks,
Olaf




--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Olaf Krueger
In reply to this post by Apache Infrastructure Team
Just an example of how the Hadoop community has handled the migration:

https://issues.apache.org/jira/browse/INFRA-17448





--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Alex Harui-2
In reply to this post by Olaf Krueger

On 1/3/19, 5:53 AM, "Olaf Krueger" <[hidden email]> wrote:

    Hi guys,
    if I understand it correctly we have to vote for the migration and we
    optionally can specify a date for it.
   
    However,
    - Does anybody know if this migration will break anything?
Well, that's what we should be brainstorming.  I think we will need someone to:
-update the website links to the repos
-update any Flex jobs on builds.a.o.
-check for links to the repos in readme files

FWIW, I turned off my CI server for Flex several weeks ago just to see if anybody would notice.  Nobody noticed, so I'm tempted to just let it sit until we actually need it and then we'll have to go update those jobs.

    - Do we need to keep the FlexJS repositories (Maybe they can be deleted
    because they moved to Royale)?

We should move them.  You never know if someone is using them.

My 2 cents,
-Alex
 

Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

piotrz
I the other words it looks like we should just wait for that migration.
Once they do that I will update all those links.

Piotr

On Thu, Jan 3, 2019, 7:33 PM Alex Harui <[hidden email]> wrote:

>
> On 1/3/19, 5:53 AM, "Olaf Krueger" <[hidden email]> wrote:
>
>     Hi guys,
>     if I understand it correctly we have to vote for the migration and we
>     optionally can specify a date for it.
>
>     However,
>     - Does anybody know if this migration will break anything?
> Well, that's what we should be brainstorming.  I think we will need
> someone to:
> -update the website links to the repos
> -update any Flex jobs on builds.a.o.
> -check for links to the repos in readme files
>
> FWIW, I turned off my CI server for Flex several weeks ago just to see if
> anybody would notice.  Nobody noticed, so I'm tempted to just let it sit
> until we actually need it and then we'll have to go update those jobs.
>
>     - Do we need to keep the FlexJS repositories (Maybe they can be deleted
>     because they moved to Royale)?
>
> We should move them.  You never know if someone is using them.
>
> My 2 cents,
> -Alex
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Olaf Krueger
In reply to this post by Alex Harui-2
Hi,

> -update any Flex jobs on builds.a.o.

What is builds.a.o?

> FWIW, I turned off my CI server for Flex several weeks ago

Ok, for what was it used for?
Do we need it for making a release?

Is the installer affected by the migration?

Thanks,
Olaf



--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Alex Harui-2


On 1/3/19, 12:47 PM, "Olaf Krueger" <[hidden email]> wrote:

    Hi,
   
    > -update any Flex jobs on builds.a.o.
   
    What is builds.a.o?
   
Apache runs a CI service at builds.a.o.  Royale uses it for Maven.  We use my other CI server for Ant because there are some issues with running Flash for tests on builds.a.o.

    > FWIW, I turned off my CI server for Flex several weeks ago
   
    Ok, for what was it used for?
    Do we need it for making a release?
   
It was used for Flex nightly builds and checking the MD5s on the Adobe downloads.  We don't need it for making a release.  It might have helped knowing that some other Windows machine can build the source code into release packages.

    Is the installer affected by the migration?
   
I can't think of any connection between the Installer and Apache Git, but that is a good example of the kinds of questions we should be asking.

-Alex
   
   
    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-development.2333347.n4.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C526ad293d15c4103e80108d671bcb3bb%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636821452613734956&amp;sdata=n876%2BNgV1Az8%2BxL94j7%2BIrAGEMZ8mLnBpCuNlOuVkOk%3D&amp;reserved=0
   

Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Alex Harui-2
In reply to this post by piotrz
They are asking for permission to do it early.  We should oblige and agree that they can move early and we have the people to fix up the things that need fixing.  If we wait, we will have more trouble getting their attention if things go wrong for lots of projects at one time.

-Alex

On 1/3/19, 12:00 PM, "Piotr Zarzycki" <[hidden email]> wrote:

    I the other words it looks like we should just wait for that migration.
    Once they do that I will update all those links.
   
    Piotr
   
    On Thu, Jan 3, 2019, 7:33 PM Alex Harui <[hidden email]> wrote:
   
    >
    > On 1/3/19, 5:53 AM, "Olaf Krueger" <[hidden email]> wrote:
    >
    >     Hi guys,
    >     if I understand it correctly we have to vote for the migration and we
    >     optionally can specify a date for it.
    >
    >     However,
    >     - Does anybody know if this migration will break anything?
    > Well, that's what we should be brainstorming.  I think we will need
    > someone to:
    > -update the website links to the repos
    > -update any Flex jobs on builds.a.o.
    > -check for links to the repos in readme files
    >
    > FWIW, I turned off my CI server for Flex several weeks ago just to see if
    > anybody would notice.  Nobody noticed, so I'm tempted to just let it sit
    > until we actually need it and then we'll have to go update those jobs.
    >
    >     - Do we need to keep the FlexJS repositories (Maybe they can be deleted
    >     because they moved to Royale)?
    >
    > We should move them.  You never know if someone is using them.
    >
    > My 2 cents,
    > -Alex
    >
    >
    >
   

Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Olaf Krueger
In reply to this post by Alex Harui-2
Thanks for the explanation, Alex!

> We should oblige and agree that they can move early...

Just to make sure that we all are on the same path:
Even if we expect some minor issues we want to let them do the migration
ASAP.
Each upcoming issue will be fixed after the migration is done.

If that's right, I guess we should start a vote and when it's done I would
file an INFRA JIRA which includes a link to the vote to let them know that
they can migrate, right?

Thanks,
Olaf





--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Carlos Rovira-3
Hi Olaf,

IMHO, is a mandatory request for their part, so don't think we need to
vote. They will do unilaterally. I think they request us to support the
migration.



El vie., 4 ene. 2019 a las 8:19, Olaf Krueger (<[hidden email]>)
escribió:

> Thanks for the explanation, Alex!
>
> > We should oblige and agree that they can move early...
>
> Just to make sure that we all are on the same path:
> Even if we expect some minor issues we want to let them do the migration
> ASAP.
> Each upcoming issue will be fixed after the migration is done.
>
> If that's right, I guess we should start a vote and when it's done I would
> file an INFRA JIRA which includes a link to the vote to let them know that
> they can migrate, right?
>
> Thanks,
> Olaf
>
>
>
>
>
> --
> Sent from: http://apache-flex-development.2333347.n4.nabble.com/
>


--
Carlos Rovira
http://about.me/carlosrovira
Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Olaf Krueger
Hi Carlos,
yes, the migration is mandatory.
They will do the migration after February 7th without any warnings.

But my understanding is, that they asked the communities to do it before
this deadline orderly in order to avoid as much trouble as possible.
Without any feedback from the communities, they won't migrate before
February 7th.

Of course, we could wait until February 7th, but the danger is that INFRA
could be very busy then with fixing whatever other issues from other
communities.

If we want to let them do the migration earlier, we need to get a consensus
about this and we need to inform INFRA.
To get a consensus I thought a simple vote is a proper way.

Makes sense? ...of course, I could be wrong ;-)

Thanks,
Olaf










--
Sent from: http://apache-flex-development.2333347.n4.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org

Carlos Rovira-3
Hi Olaf,

ok, I was interpreting his email in a different way. Anyway is good to make
consensus

thanks

Carlos



El vie., 4 ene. 2019 a las 11:37, Olaf Krueger (<[hidden email]>)
escribió:

> Hi Carlos,
> yes, the migration is mandatory.
> They will do the migration after February 7th without any warnings.
>
> But my understanding is, that they asked the communities to do it before
> this deadline orderly in order to avoid as much trouble as possible.
> Without any feedback from the communities, they won't migrate before
> February 7th.
>
> Of course, we could wait until February 7th, but the danger is that INFRA
> could be very busy then with fixing whatever other issues from other
> communities.
>
> If we want to let them do the migration earlier, we need to get a consensus
> about this and we need to inform INFRA.
> To get a consensus I thought a simple vote is a proper way.
>
> Makes sense? ...of course, I could be wrong ;-)
>
> Thanks,
> Olaf
>
>
>
>
>
>
>
>
>
>
> --
> Sent from: http://apache-flex-development.2333347.n4.nabble.com/
>


--
Carlos Rovira
http://about.me/carlosrovira