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.
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,
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.247.n4.nabble.com/
On 1/3/19, 5:53 AM, "Olaf Krueger" 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 brainstormi
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 wrote:
>
> On 1/3/19, 5:53 AM, "Olaf Krueger" wrote:
>
> Hi guys,
> if I understand it correctly we have to vote for t
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-developme
On 1/3/19, 12:47 PM, "Olaf Krueger" 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
tes
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
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 r
