[jira] [Commented] (ARROW-17552) [Dev] Remove "master" from default_branch property of Target class in core.py after migration to "main" as the default Git branch
[
https://issues.apache.org/jira/browse/ARROW-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17640243#comment-17640243
]
Kevin Gurney commented on ARROW-17552:
--
For clarity - I am leaving this as Unassigned until the other issues it depends
on are resolved to keep it clear which issues are actively being worked on vs.
which are planned for the future.
> [Dev] Remove "master" from default_branch property of Target class in core.py
> after migration to "main" as the default Git branch
> -
>
> Key: ARROW-17552
> URL: https://issues.apache.org/jira/browse/ARROW-17552
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Affects Versions: 10.0.0
>Reporter: Kevin Gurney
>Priority: Minor
>
> As a follow up to [ARROW-15693|https://github.com/apache/arrow/pull/13975],
> support for the name "master" in the {{default_branch}} property of the
> {{Target}} class defined in {{dev/archery/archery/crossbow/core.py}} should
> be removed after the migration to "main" as the default Git branch is
> complete.
> Making this change will also require updating the implementation of the
> {{Target.is_default_branch()}} method to use the keyword {{is}} instead of
> {{in}} for checking whether on the default branch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (ARROW-18011) [Dev] Replace hard-coded string "master" with "main" in dev/archery/archery/crossbow/core.py after default branch migration
Kevin Gurney created ARROW-18011: Summary: [Dev] Replace hard-coded string "master" with "main" in dev/archery/archery/crossbow/core.py after default branch migration Key: ARROW-18011 URL: https://issues.apache.org/jira/browse/ARROW-18011 Project: Apache Arrow Issue Type: Sub-task Components: Developer Tools Reporter: Kevin Gurney [https://github.com/apache/arrow/pull/14033] uses several heuristics to determine the default Git branch name for the upstream apache/arrow project. When the heuristics fail to detect the default branch name, the strategy used in [https://github.com/apache/arrow/pull/14033] currently falls back to using the hard-coded branch name "master". After [https://github.com/apache/arrow/pull/14033] is merged and after the upstream apache/arrow GitHub repository migrates to using "main" as the default branch name, the hard-coded string "master" should be replaced with "main" inside of the implementation of the computed property "default_branch_name" of the "Repo" class in dev/archery/archery/crossbow/core.py. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARROW-17552) [Dev] Remove "master" from default_branch property of Target class in core.py after migration to "main" as the default Git branch
Kevin Gurney created ARROW-17552:
Summary: [Dev] Remove "master" from default_branch property of
Target class in core.py after migration to "main" as the default Git branch
Key: ARROW-17552
URL: https://issues.apache.org/jira/browse/ARROW-17552
Project: Apache Arrow
Issue Type: Sub-task
Components: Developer Tools
Affects Versions: 10.0.0
Reporter: Kevin Gurney
Assignee: Kevin Gurney
As a follow up to [ARROW-15693|https://github.com/apache/arrow/pull/13975],
support for the name "master" in the {{default_branch}} property of the
{{Target}} class defined in {{dev/archery/archery/crossbow/core.py}} should be
removed after the migration to "main" as the default Git branch is complete.
Making this change will also require updating the implementation of the
{{Target.is_default_branch()}} method to use the keyword {{is}} instead of
{{in}} for checking whether on the default branch.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (ARROW-15693) [Dev] Update crossbow templates to use master or main
[ https://issues.apache.org/jira/browse/ARROW-15693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney reassigned ARROW-15693: Assignee: Kevin Gurney > [Dev] Update crossbow templates to use master or main > - > > Key: ARROW-15693 > URL: https://issues.apache.org/jira/browse/ARROW-15693 > Project: Apache Arrow > Issue Type: Sub-task > Components: Developer Tools >Reporter: Neal Richardson >Assignee: Kevin Gurney >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (ARROW-15694) [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment workflow to support being triggered when pushing to main
[
https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney closed ARROW-15694.
Merged via [https://github.com/apache/arrow-site/pull/202.]
> [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment
> workflow to support being triggered when pushing to main
>
>
> Key: ARROW-15694
> URL: https://issues.apache.org/jira/browse/ARROW-15694
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Neal Richardson
>Assignee: Kevin Gurney
>Priority: Major
> Labels: pull-request-available
> Fix For: 8.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As part of the transition away from using the name {{master}} for the default
> Git branch, we need to update the GitHub Actions website deployment workflow
> trigger.
> Since there does not appear to be any way to dynamically compute the default
> Git branch name in a GitHub Actions push trigger condition, a temporary
> workaround would be to add support for pushing to either {{master}} or
> {{{}main{}}}.
> Once Apache Infra switches the default Git branch for {{apache/arrow-site}}
> to {{{}main{}}}, we can completely remove support for triggering the GitHub
> Actions website deployment workflow on pushes to {{master}} from
> {{{}.github/workflows/deploy.yml{}}}. This follow up work is tracked by
> ARROW-15988.
> The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15694) [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment workflow to support being triggered when pushing to main
[
https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15694:
-
Labels: pull-request-available (was: )
> [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment
> workflow to support being triggered when pushing to main
>
>
> Key: ARROW-15694
> URL: https://issues.apache.org/jira/browse/ARROW-15694
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Neal Richardson
>Assignee: Kevin Gurney
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> As part of the transition away from using the name {{master}} for the default
> Git branch, we need to update the GitHub Actions website deployment workflow
> trigger.
> Since there does not appear to be any way to dynamically compute the default
> Git branch name in a GitHub Actions push trigger condition, a temporary
> workaround would be to add support for pushing to either {{master}} or
> {{{}main{}}}.
> Once Apache Infra switches the default Git branch for {{apache/arrow-site}}
> to {{{}main{}}}, we can completely remove support for triggering the GitHub
> Actions website deployment workflow on pushes to {{master}} from
> {{{}.github/workflows/deploy.yml{}}}. This follow up work is tracked by
> ARROW-15988.
> The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ARROW-15991) Remove mentions of master branch from Apache Arrow website content
Kevin Gurney created ARROW-15991:
Summary: Remove mentions of master branch from Apache Arrow
website content
Key: ARROW-15991
URL: https://issues.apache.org/jira/browse/ARROW-15991
Project: Apache Arrow
Issue Type: Sub-task
Components: Website
Reporter: Kevin Gurney
Assignee: Kevin Gurney
This is a follow up task to
[ARROW-15694|https://issues.apache.org/jira/browse/ARROW-15694] and
[ARROW-15988|https://issues.apache.org/jira/browse/ARROW-15988].
We need to update the actual content of the Apache Arrow website to no longer
refer to the "master" branch. This includes updating links, text snippets, and
the {{README.md}} for {{{}arrow-site{}}}. There may also be other files that
need to be updated, as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15991) [Website] Remove mentions of master branch from Apache Arrow website content
[
https://issues.apache.org/jira/browse/ARROW-15991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15991:
-
Summary: [Website] Remove mentions of master branch from Apache Arrow
website content (was: Remove mentions of master branch from Apache Arrow
website content)
> [Website] Remove mentions of master branch from Apache Arrow website content
>
>
> Key: ARROW-15991
> URL: https://issues.apache.org/jira/browse/ARROW-15991
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Website
>Reporter: Kevin Gurney
>Assignee: Kevin Gurney
>Priority: Major
>
> This is a follow up task to
> [ARROW-15694|https://issues.apache.org/jira/browse/ARROW-15694] and
> [ARROW-15988|https://issues.apache.org/jira/browse/ARROW-15988].
> We need to update the actual content of the Apache Arrow website to no longer
> refer to the "master" branch. This includes updating links, text snippets,
> and the {{README.md}} for {{{}arrow-site{}}}. There may also be other files
> that need to be updated, as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15694) [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment workflow to support being triggered when pushing to main
[
https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15694:
-
Description:
As part of the transition away from using the name {{master}} for the default
Git branch, we need to update the GitHub Actions website deployment workflow
trigger.
Since there does not appear to be any way to dynamically compute the default
Git branch name in a GitHub Actions push trigger condition, a temporary
workaround would be to add support for pushing to either {{master}} or
{{{}main{}}}.
Once Apache Infra switches the default Git branch for {{apache/arrow-site}} to
{{{}main{}}}, we can completely remove support for triggering the GitHub
Actions website deployment workflow on pushes to {{master}} from
{{{}.github/workflows/deploy.yml{}}}. This follow up work is tracked by
ARROW-15988.
The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
was:
As part of the transition away from using the name {{master}} for the default
Git branch, we need to update the GitHub Actions website deployment workflow
trigger.
Since there does not appear to be any way to dynamically compute the default
Git branch name in a GitHub Actions push trigger condition, a temporary
workaround would be to add support for pushing to either {{master}} or
{{{}main{}}}.
Once Apache Infra switches the default Git branch for {{apache/arrow-site}} to
{{{}main{}}}, we can completely remove support for triggering the GitHub
Actions website deployment workflow from {{{}.github/workflows/deploy.yml{}}}.
This follow up work is tracked by: ARROW-15988.
The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
> [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment
> workflow to support being triggered when pushing to main
>
>
> Key: ARROW-15694
> URL: https://issues.apache.org/jira/browse/ARROW-15694
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Neal Richardson
>Assignee: Kevin Gurney
>Priority: Major
>
> As part of the transition away from using the name {{master}} for the default
> Git branch, we need to update the GitHub Actions website deployment workflow
> trigger.
> Since there does not appear to be any way to dynamically compute the default
> Git branch name in a GitHub Actions push trigger condition, a temporary
> workaround would be to add support for pushing to either {{master}} or
> {{{}main{}}}.
> Once Apache Infra switches the default Git branch for {{apache/arrow-site}}
> to {{{}main{}}}, we can completely remove support for triggering the GitHub
> Actions website deployment workflow on pushes to {{master}} from
> {{{}.github/workflows/deploy.yml{}}}. This follow up work is tracked by
> ARROW-15988.
> The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15694) [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment workflow to support being triggered when pushing to main
[
https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15694:
-
Description:
As part of the transition away from using the name {{master}} for the default
Git branch, we need to update the GitHub Actions website deployment workflow
trigger.
Since there does not appear to be any way to dynamically compute the default
Git branch name in a GitHub Actions push trigger condition, a temporary
workaround would be to add support for pushing to either {{master}} or
{{{}main{}}}.
Once Apache Infra switches the default Git branch for {{apache/arrow-site}} to
{{{}main{}}}, we can completely remove support for triggering the GitHub
Actions website deployment workflow from {{{}.github/workflows/deploy.yml{}}}.
This follow up work is tracked by: ARROW-15988.
The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
was:
As part of the transition away from using the name {{master}} for the default
Git branch, we need to update the GitHub Actions website deployment workflow
trigger.
Since there does not appear to be any way to dynamically compute the default
Git branch name in a GitHub Actions push trigger condition, a temporary
workaround would be to add support for pushing to either {{master}} or
{{{}main{}}}.
Once Apache Infra switches the default Git branch for {{apache/arrow-site}} to
{{{}main{}}}, we can completely remove support for triggering the GitHub
Actions website deployment workflow from {{{}.github/workflows/deploy.yml{}}}.
This follow up work is tracked by:
[ARROW-15988](https://issues.apache.org/jira/browse/ARROW-15988).
The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
> [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment
> workflow to support being triggered when pushing to main
>
>
> Key: ARROW-15694
> URL: https://issues.apache.org/jira/browse/ARROW-15694
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Neal Richardson
>Assignee: Kevin Gurney
>Priority: Major
>
> As part of the transition away from using the name {{master}} for the default
> Git branch, we need to update the GitHub Actions website deployment workflow
> trigger.
> Since there does not appear to be any way to dynamically compute the default
> Git branch name in a GitHub Actions push trigger condition, a temporary
> workaround would be to add support for pushing to either {{master}} or
> {{{}main{}}}.
> Once Apache Infra switches the default Git branch for {{apache/arrow-site}}
> to {{{}main{}}}, we can completely remove support for triggering the GitHub
> Actions website deployment workflow from
> {{{}.github/workflows/deploy.yml{}}}. This follow up work is tracked by:
> ARROW-15988.
> The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15694) [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment workflow to support being triggered when pushing to main
[
https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15694:
-
Summary: [Dev] Update apache/arrow-site GitHub Actions deploy.yml website
deployment workflow to support being triggered when pushing to main (was:
[Dev] Update arrow-site GitHub Actions workflows that hard-code master as the
default Git branch)
> [Dev] Update apache/arrow-site GitHub Actions deploy.yml website deployment
> workflow to support being triggered when pushing to main
>
>
> Key: ARROW-15694
> URL: https://issues.apache.org/jira/browse/ARROW-15694
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Neal Richardson
>Assignee: Kevin Gurney
>Priority: Major
>
> As part of the transition away from using the name {{master}} for the default
> Git branch, we need to update the GitHub Actions website deployment workflow
> trigger.
> Since there does not appear to be any way to dynamically compute the default
> Git branch name in a GitHub Actions push trigger condition, a temporary
> workaround would be to add support for pushing to either {{master}} or
> {{{}main{}}}.
> Once Apache Infra switches the default Git branch for {{apache/arrow-site}}
> to {{{}main{}}}, we can completely remove support for triggering the GitHub
> Actions website deployment workflow from
> {{{}.github/workflows/deploy.yml{}}}. This follow up work is tracked by:
> [ARROW-15988](https://issues.apache.org/jira/browse/ARROW-15988).
> The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15694) [Dev] Update arrow-site GitHub Actions workflows that hard-code master as the default Git branch
[
https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15694:
-
Description:
As part of the transition away from using the name {{master}} for the default
Git branch, we need to update the GitHub Actions website deployment workflow
trigger.
Since there does not appear to be any way to dynamically compute the default
Git branch name in a GitHub Actions push trigger condition, a temporary
workaround would be to add support for pushing to either {{master}} or
{{{}main{}}}.
Once Apache Infra switches the default Git branch for {{apache/arrow-site}} to
{{{}main{}}}, we can completely remove support for triggering the GitHub
Actions website deployment workflow from {{{}.github/workflows/deploy.yml{}}}.
This follow up work is tracked by:
[ARROW-15988](https://issues.apache.org/jira/browse/ARROW-15988).
The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
was:
Update the GitHub Actions workflow for deploying the Apache Arrow website to
the {{asf-site}} branch to dynamically compute the default Git branch name.
The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
> [Dev] Update arrow-site GitHub Actions workflows that hard-code master as the
> default Git branch
>
>
> Key: ARROW-15694
> URL: https://issues.apache.org/jira/browse/ARROW-15694
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Neal Richardson
>Assignee: Kevin Gurney
>Priority: Major
>
> As part of the transition away from using the name {{master}} for the default
> Git branch, we need to update the GitHub Actions website deployment workflow
> trigger.
> Since there does not appear to be any way to dynamically compute the default
> Git branch name in a GitHub Actions push trigger condition, a temporary
> workaround would be to add support for pushing to either {{master}} or
> {{{}main{}}}.
> Once Apache Infra switches the default Git branch for {{apache/arrow-site}}
> to {{{}main{}}}, we can completely remove support for triggering the GitHub
> Actions website deployment workflow from
> {{{}.github/workflows/deploy.yml{}}}. This follow up work is tracked by:
> [ARROW-15988](https://issues.apache.org/jira/browse/ARROW-15988).
> The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15988) [DEV] Remove support for triggering GitHub Actions apache/arrow-site website deployment workflow when pushing to master
[
https://issues.apache.org/jira/browse/ARROW-15988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15988:
-
Component/s: Developer Tools
(was: Website)
Summary: [DEV] Remove support for triggering GitHub Actions
apache/arrow-site website deployment workflow when pushing to master (was:
Remove support for triggering GitHub Actions apache/arrow-site website
deployment workflow when pushing to master)
> [DEV] Remove support for triggering GitHub Actions apache/arrow-site website
> deployment workflow when pushing to master
> ---
>
> Key: ARROW-15988
> URL: https://issues.apache.org/jira/browse/ARROW-15988
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Kevin Gurney
>Assignee: Kevin Gurney
>Priority: Major
>
> This is a follow up to
> [ARROW-15694|https://issues.apache.org/jira/browse/ARROW-15694].
> Once Apache Infra switches the default Git branch from master to main in
> apache/arrow-site, we should completely remove support for triggering the
> deploy.yml CI workflow on a push to master.
> This should be straightforward and would involve removing master from the
> {{.github/workflows/deploy.yml}} push trigger condition.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15988) [Dev] Remove support for triggering GitHub Actions apache/arrow-site website deployment workflow when pushing to master
[
https://issues.apache.org/jira/browse/ARROW-15988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15988:
-
Summary: [Dev] Remove support for triggering GitHub Actions
apache/arrow-site website deployment workflow when pushing to master (was:
[DEV] Remove support for triggering GitHub Actions apache/arrow-site website
deployment workflow when pushing to master)
> [Dev] Remove support for triggering GitHub Actions apache/arrow-site website
> deployment workflow when pushing to master
> ---
>
> Key: ARROW-15988
> URL: https://issues.apache.org/jira/browse/ARROW-15988
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Kevin Gurney
>Assignee: Kevin Gurney
>Priority: Major
>
> This is a follow up to
> [ARROW-15694|https://issues.apache.org/jira/browse/ARROW-15694].
> Once Apache Infra switches the default Git branch from master to main in
> apache/arrow-site, we should completely remove support for triggering the
> deploy.yml CI workflow on a push to master.
> This should be straightforward and would involve removing master from the
> {{.github/workflows/deploy.yml}} push trigger condition.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (ARROW-15988) Remove support for triggering GitHub Actions apache/arrow-site website deployment workflow when pushing to master
Kevin Gurney created ARROW-15988:
Summary: Remove support for triggering GitHub Actions
apache/arrow-site website deployment workflow when pushing to master
Key: ARROW-15988
URL: https://issues.apache.org/jira/browse/ARROW-15988
Project: Apache Arrow
Issue Type: Sub-task
Components: Website
Reporter: Kevin Gurney
Assignee: Kevin Gurney
This is a follow up to
[ARROW-15694|https://issues.apache.org/jira/browse/ARROW-15694].
Once Apache Infra switches the default Git branch from master to main in
apache/arrow-site, we should completely remove support for triggering the
deploy.yml CI workflow on a push to master.
This should be straightforward and would involve removing master from the
{{.github/workflows/deploy.yml}} push trigger condition.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (ARROW-15931) [Website] Add explicit Apache LICENSE.txt and NOTICE.txt files to apache/arrow-site repository
[ https://issues.apache.org/jira/browse/ARROW-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney closed ARROW-15931. Merged in https://github.com/apache/arrow-site/pull/200. > [Website] Add explicit Apache LICENSE.txt and NOTICE.txt files to > apache/arrow-site repository > -- > > Key: ARROW-15931 > URL: https://issues.apache.org/jira/browse/ARROW-15931 > Project: Apache Arrow > Issue Type: Improvement > Components: Website >Reporter: Kevin Gurney >Assignee: Kevin Gurney >Priority: Minor > Labels: pull-request-available > Fix For: 8.0.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > To be consistent with the main apache/arrow GitHub repository (and other > Apache projects), it would be helpful to add explicit Apache LICENSE.txt and > NOTICE.txt files to the root of the apache/arrow-site repository. This would > help clear up any potential ambiguity around the licensing of the source code > for the Apache Arrow website. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARROW-15694) [Dev] Update arrow-site GitHub Actions workflows that hard-code master as the default Git branch
[
https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15694:
-
Summary: [Dev] Update arrow-site GitHub Actions workflows that hard-code
master as the default Git branch (was: [Dev] Update arrow-site GitHub Actions
workflows to work with master or main)
> [Dev] Update arrow-site GitHub Actions workflows that hard-code master as the
> default Git branch
>
>
> Key: ARROW-15694
> URL: https://issues.apache.org/jira/browse/ARROW-15694
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Neal Richardson
>Assignee: Kevin Gurney
>Priority: Major
>
> Update the GitHub Actions workflow for deploying the Apache Arrow website to
> the {{asf-site}} branch to dynamically compute the default Git branch name.
> The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15694) [Dev] Update arrow-site GitHub Actions workflows to work with master or main
[
https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15694:
-
Summary: [Dev] Update arrow-site GitHub Actions workflows to work with
master or main (was: [Dev] Update arrow-site workflows to work with master or
main)
> [Dev] Update arrow-site GitHub Actions workflows to work with master or main
>
>
> Key: ARROW-15694
> URL: https://issues.apache.org/jira/browse/ARROW-15694
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Neal Richardson
>Assignee: Kevin Gurney
>Priority: Major
>
> Update the GitHub Actions workflow for deploying the Apache Arrow website to
> the {{asf-site}} branch to dynamically compute the default Git branch name.
> The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15694) [Dev] Update arrow-site workflows to work with master or main
[
https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-15694:
-
Description:
Update the GitHub Actions workflow for deploying the Apache Arrow website to
the {{asf-site}} branch to dynamically compute the default Git branch name.
The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
was:
Update the GitHub Actions workflow for deploying the Apache Arrow website to
the `arrow-site/asf-site` branch to dynamically compute the default Git branch
name.
The main file that will need updating is
[.github/workflows/deploy.yml|[https://github.com/apache/arrow-site/blob/d99e3012a95be3d6f89d8f2cf849516154ae144e/.github/workflows/deploy.yml]].
> [Dev] Update arrow-site workflows to work with master or main
> -
>
> Key: ARROW-15694
> URL: https://issues.apache.org/jira/browse/ARROW-15694
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Developer Tools
>Reporter: Neal Richardson
>Assignee: Kevin Gurney
>Priority: Major
>
> Update the GitHub Actions workflow for deploying the Apache Arrow website to
> the {{asf-site}} branch to dynamically compute the default Git branch name.
> The main file that will need updating is {{{}.github/workflows/deploy.yml{}}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (ARROW-15694) [Dev] Update arrow-site workflows to work with master or main
[ https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney updated ARROW-15694: - Description: Update the GitHub Actions workflow for deploying the Apache Arrow website to the `arrow-site/asf-site` branch to dynamically compute the default Git branch name. The main file that will need updating is [.github/workflows/deploy.yml](https://github.com/apache/arrow-site/blob/d99e3012a95be3d6f89d8f2cf849516154ae144e/.github/workflows/deploy.yml). > [Dev] Update arrow-site workflows to work with master or main > - > > Key: ARROW-15694 > URL: https://issues.apache.org/jira/browse/ARROW-15694 > Project: Apache Arrow > Issue Type: Sub-task > Components: Developer Tools >Reporter: Neal Richardson >Assignee: Kevin Gurney >Priority: Major > > Update the GitHub Actions workflow for deploying the Apache Arrow website to > the `arrow-site/asf-site` branch to dynamically compute the default Git > branch name. > The main file that will need updating is > [.github/workflows/deploy.yml](https://github.com/apache/arrow-site/blob/d99e3012a95be3d6f89d8f2cf849516154ae144e/.github/workflows/deploy.yml). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARROW-15694) [Dev] Update arrow-site workflows to work with master or main
[ https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney updated ARROW-15694: - Description: Update the GitHub Actions workflow for deploying the Apache Arrow website to the `arrow-site/asf-site` branch to dynamically compute the default Git branch name. The main file that will need updating is [.github/workflows/deploy.yml|[https://github.com/apache/arrow-site/blob/d99e3012a95be3d6f89d8f2cf849516154ae144e/.github/workflows/deploy.yml]]. was: Update the GitHub Actions workflow for deploying the Apache Arrow website to the `arrow-site/asf-site` branch to dynamically compute the default Git branch name. The main file that will need updating is [.github/workflows/deploy.yml](https://github.com/apache/arrow-site/blob/d99e3012a95be3d6f89d8f2cf849516154ae144e/.github/workflows/deploy.yml). > [Dev] Update arrow-site workflows to work with master or main > - > > Key: ARROW-15694 > URL: https://issues.apache.org/jira/browse/ARROW-15694 > Project: Apache Arrow > Issue Type: Sub-task > Components: Developer Tools >Reporter: Neal Richardson >Assignee: Kevin Gurney >Priority: Major > > Update the GitHub Actions workflow for deploying the Apache Arrow website to > the `arrow-site/asf-site` branch to dynamically compute the default Git > branch name. > The main file that will need updating is > [.github/workflows/deploy.yml|[https://github.com/apache/arrow-site/blob/d99e3012a95be3d6f89d8f2cf849516154ae144e/.github/workflows/deploy.yml]]. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARROW-15931) [Website] Add explicit Apache LICENSE.txt and NOTICE.txt files to apache/arrow-site repository
[ https://issues.apache.org/jira/browse/ARROW-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney updated ARROW-15931: - Labels: pull-request-available (was: ) > [Website] Add explicit Apache LICENSE.txt and NOTICE.txt files to > apache/arrow-site repository > -- > > Key: ARROW-15931 > URL: https://issues.apache.org/jira/browse/ARROW-15931 > Project: Apache Arrow > Issue Type: Improvement > Components: Website >Reporter: Kevin Gurney >Assignee: Kevin Gurney >Priority: Minor > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > To be consistent with the main apache/arrow GitHub repository (and other > Apache projects), it would be helpful to add explicit Apache LICENSE.txt and > NOTICE.txt files to the root of the apache/arrow-site repository. This would > help clear up any potential ambiguity around the licensing of the source code > for the Apache Arrow website. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARROW-15931) [Website] Add explicit Apache LICENSE.txt and NOTICE.txt file to apache/arrow-site repository
[ https://issues.apache.org/jira/browse/ARROW-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney updated ARROW-15931: - Description: To be consistent with the main apache/arrow GitHub repository (and other Apache projects), it would be helpful to add explicit Apache LICENSE.txt and NOTICE.txt files to the root of the apache/arrow-site repository. This would help clear up any potential ambiguity around the licensing of the source code for the Apache Arrow website. (was: To be consistent with the main apache/arrow GitHub repository (and other Apache projects), it would be helpful to add an explicit Apache LICENSE.txt file to the root of the apache/arrow-site repository. This would help clear up any potential ambiguity around the licensing of the source code for the Apache Arrow website.) Summary: [Website] Add explicit Apache LICENSE.txt and NOTICE.txt file to apache/arrow-site repository (was: [Website] Add explicit Apache LICENSE.txt file to apache/arrow-site repository) > [Website] Add explicit Apache LICENSE.txt and NOTICE.txt file to > apache/arrow-site repository > - > > Key: ARROW-15931 > URL: https://issues.apache.org/jira/browse/ARROW-15931 > Project: Apache Arrow > Issue Type: Improvement > Components: Website >Reporter: Kevin Gurney >Assignee: Kevin Gurney >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > To be consistent with the main apache/arrow GitHub repository (and other > Apache projects), it would be helpful to add explicit Apache LICENSE.txt and > NOTICE.txt files to the root of the apache/arrow-site repository. This would > help clear up any potential ambiguity around the licensing of the source code > for the Apache Arrow website. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARROW-15931) [Website] Add explicit Apache LICENSE.txt and NOTICE.txt files to apache/arrow-site repository
[ https://issues.apache.org/jira/browse/ARROW-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney updated ARROW-15931: - Summary: [Website] Add explicit Apache LICENSE.txt and NOTICE.txt files to apache/arrow-site repository (was: [Website] Add explicit Apache LICENSE.txt and NOTICE.txt file to apache/arrow-site repository) > [Website] Add explicit Apache LICENSE.txt and NOTICE.txt files to > apache/arrow-site repository > -- > > Key: ARROW-15931 > URL: https://issues.apache.org/jira/browse/ARROW-15931 > Project: Apache Arrow > Issue Type: Improvement > Components: Website >Reporter: Kevin Gurney >Assignee: Kevin Gurney >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > To be consistent with the main apache/arrow GitHub repository (and other > Apache projects), it would be helpful to add explicit Apache LICENSE.txt and > NOTICE.txt files to the root of the apache/arrow-site repository. This would > help clear up any potential ambiguity around the licensing of the source code > for the Apache Arrow website. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (ARROW-15931) [Website] Add explicit Apache LICENSE.txt file to apache/arrow-site repository
[ https://issues.apache.org/jira/browse/ARROW-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17506566#comment-17506566 ] Kevin Gurney commented on ARROW-15931: -- Yes, I'll update the pull request to add a NOTICE file, too. Thank you for suggesting this, [~kou]! > [Website] Add explicit Apache LICENSE.txt file to apache/arrow-site repository > -- > > Key: ARROW-15931 > URL: https://issues.apache.org/jira/browse/ARROW-15931 > Project: Apache Arrow > Issue Type: Improvement > Components: Website >Reporter: Kevin Gurney >Assignee: Kevin Gurney >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > To be consistent with the main apache/arrow GitHub repository (and other > Apache projects), it would be helpful to add an explicit Apache LICENSE.txt > file to the root of the apache/arrow-site repository. This would help clear > up any potential ambiguity around the licensing of the source code for the > Apache Arrow website. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (ARROW-15694) [Dev] Update arrow-site workflows to work with master or main
[ https://issues.apache.org/jira/browse/ARROW-15694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney reassigned ARROW-15694: Assignee: Kevin Gurney > [Dev] Update arrow-site workflows to work with master or main > - > > Key: ARROW-15694 > URL: https://issues.apache.org/jira/browse/ARROW-15694 > Project: Apache Arrow > Issue Type: Sub-task > Components: Developer Tools >Reporter: Neal Richardson >Assignee: Kevin Gurney >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARROW-15931) Add explicit Apache LICENSE.txt file to apache/arrow-site repository
[ https://issues.apache.org/jira/browse/ARROW-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney updated ARROW-15931: - Summary: Add explicit Apache LICENSE.txt file to apache/arrow-site repository (was: Add explicit Apache LICENSE file to apache/arrow-site repository) > Add explicit Apache LICENSE.txt file to apache/arrow-site repository > > > Key: ARROW-15931 > URL: https://issues.apache.org/jira/browse/ARROW-15931 > Project: Apache Arrow > Issue Type: Improvement > Components: Website >Reporter: Kevin Gurney >Assignee: Kevin Gurney >Priority: Minor > > To be consistent with the main apache/arrow GitHub repository (and other > Apache projects), it would be helpful to add an explicit Apache LICENSE.txt > file to the root of the apache/arrow-site repository. This would help clear > up any potential ambiguity around the licensing of the source code for the > Apache Arrow website. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARROW-15931) Add explicit Apache LICENSE file to apache/arrow-site repository
[ https://issues.apache.org/jira/browse/ARROW-15931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney updated ARROW-15931: - Description: To be consistent with the main apache/arrow GitHub repository (and other Apache projects), it would be helpful to add an explicit Apache LICENSE.txt file to the root of the apache/arrow-site repository. This would help clear up any potential ambiguity around the licensing of the source code for the Apache Arrow website. (was: To be consistent with the main apache/arrow GitHub repository (and other Apache projects), it would be helpful to add an explicit Apache LICENSE file to the root of the apache/arrow-site repository. This would help clear up any potential ambiguity around the licensing of the source code for the Apache Arrow website.) > Add explicit Apache LICENSE file to apache/arrow-site repository > > > Key: ARROW-15931 > URL: https://issues.apache.org/jira/browse/ARROW-15931 > Project: Apache Arrow > Issue Type: Improvement > Components: Website >Reporter: Kevin Gurney >Assignee: Kevin Gurney >Priority: Minor > > To be consistent with the main apache/arrow GitHub repository (and other > Apache projects), it would be helpful to add an explicit Apache LICENSE.txt > file to the root of the apache/arrow-site repository. This would help clear > up any potential ambiguity around the licensing of the source code for the > Apache Arrow website. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARROW-15931) Add explicit Apache LICENSE file to apache/arrow-site repository
Kevin Gurney created ARROW-15931: Summary: Add explicit Apache LICENSE file to apache/arrow-site repository Key: ARROW-15931 URL: https://issues.apache.org/jira/browse/ARROW-15931 Project: Apache Arrow Issue Type: Improvement Components: Website Reporter: Kevin Gurney Assignee: Kevin Gurney To be consistent with the main apache/arrow GitHub repository (and other Apache projects), it would be helpful to add an explicit Apache LICENSE file to the root of the apache/arrow-site repository. This would help clear up any potential ambiguity around the licensing of the source code for the Apache Arrow website. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARROW-13204) [MATLAB] Update documentation for the MATLAB Interface to reflect latest CMake build system changes
[ https://issues.apache.org/jira/browse/ARROW-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney updated ARROW-13204: - Description: The MATLAB Interface should have clear documentation detailing how to build and run the interface on all platforms using the latest CMake build system changes merged in [https://github.com/apache/arrow/pull/12004.] The current documentation is out of date and is in need of some quality of life improvements as we transition toward building out the MATLAB interface beyond just supporting basic Feather file reading and writing. was: [https://github.com/apache/arrow/pull/10614] integrates GoogleTest into the CMake build system to support building and running C++ tests for the MATLAB Interface. The MATLAB interface should have clear documentation detailing how to build and run the C++ tests on all platforms. This should include instructions for building with and without specifying a custom `GTEST_ROOT` value. Summary: [MATLAB] Update documentation for the MATLAB Interface to reflect latest CMake build system changes (was: [MATLAB] Add documentation for building and running C++ tests) > [MATLAB] Update documentation for the MATLAB Interface to reflect latest > CMake build system changes > --- > > Key: ARROW-13204 > URL: https://issues.apache.org/jira/browse/ARROW-13204 > Project: Apache Arrow > Issue Type: Task > Components: MATLAB >Reporter: Kevin Gurney >Assignee: Kevin Gurney >Priority: Minor > > The MATLAB Interface should have clear documentation detailing how to build > and run the interface on all platforms using the latest CMake build system > changes merged in [https://github.com/apache/arrow/pull/12004.] > The current documentation is out of date and is in need of some quality of > life improvements as we transition toward building out the MATLAB interface > beyond just supporting basic Feather file reading and writing. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (ARROW-13658) [MATLAB] Reduce MATLAB CI Build Time by using ccache
Kevin Gurney created ARROW-13658: Summary: [MATLAB] Reduce MATLAB CI Build Time by using ccache Key: ARROW-13658 URL: https://issues.apache.org/jira/browse/ARROW-13658 Project: Apache Arrow Issue Type: Improvement Components: MATLAB Reporter: Kevin Gurney Assignee: Kevin Gurney As part of ARROW-13202, we investigated approaches for reducing the build time of MATLAB Interface CI jobs. When doing clean builds of the MATLAB Interface locally, using [ccache|https://ccache.dev/] substantially reduced overall build time. We can follow the general approach used by other language bindings to enable the use of ccache in the MATLAB Interface GitHub Actions workflow. For example: [.github/workflows/cpp.yml|https://github.com/apache/arrow/blob/48f42e94ce8604195c1b90c4666baa1d302d3f8a/.github/workflows/cpp.yml#L301] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARROW-13647) [MATLAB] Reduce MATLAB CI Build Time by Building Arrow C++ Libraries separately and using Packaged GoogleTest
Kevin Gurney created ARROW-13647: Summary: [MATLAB] Reduce MATLAB CI Build Time by Building Arrow C++ Libraries separately and using Packaged GoogleTest Key: ARROW-13647 URL: https://issues.apache.org/jira/browse/ARROW-13647 Project: Apache Arrow Issue Type: Improvement Components: MATLAB Reporter: Kevin Gurney Assignee: Kevin Gurney As part of ARROW-13202, we investigated approaches for reducing the build time of MATLAB Interface CI jobs. Right now we build and run the the Arrow C++ tests as part of the MATLAB Interface build in order to make use of the bundled GoogleTest binaries. It may help to reduce overall build times if we instead build just the minimal Arrow C++ libraries (without the C++ tests) and install GoogleTest on the GitHub Actions Runner using apt-get. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARROW-13202) [MATLAB] Enable GitHub Actions CI for MATLAB Interface on Linux
[ https://issues.apache.org/jira/browse/ARROW-13202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Gurney updated ARROW-13202: - Description: We need to enable CI and Testing for MATLAB submissions to the [Apache Arrow project|https://github.com/apache/arrow] on GitHub. This is one part of the task to come up with the necessary steps for Linux. (was: We need to enable CI and Testing for MATLAB submissions to the [Apache Arrow project|https://github.com/apache/arrow] on GitHub. This is one part of the task to come up with the necessary steps for Debian.) Summary: [MATLAB] Enable GitHub Actions CI for MATLAB Interface on Linux (was: [MATLAB] Enable CI to build using CMAKE on Debian for MATLAB submissions) > [MATLAB] Enable GitHub Actions CI for MATLAB Interface on Linux > --- > > Key: ARROW-13202 > URL: https://issues.apache.org/jira/browse/ARROW-13202 > Project: Apache Arrow > Issue Type: Task > Components: MATLAB >Reporter: Sreehari Hegden >Assignee: Sreehari Hegden >Priority: Minor > > We need to enable CI and Testing for MATLAB submissions to the [Apache Arrow > project|https://github.com/apache/arrow] on GitHub. This is one part of the > task to come up with the necessary steps for Linux. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ARROW-13204) [MATLAB] Add documentation for building and running C++ tests
Kevin Gurney created ARROW-13204: Summary: [MATLAB] Add documentation for building and running C++ tests Key: ARROW-13204 URL: https://issues.apache.org/jira/browse/ARROW-13204 Project: Apache Arrow Issue Type: Task Components: MATLAB Reporter: Kevin Gurney Assignee: Kevin Gurney [https://github.com/apache/arrow/pull/10614] integrates GoogleTest into the CMake build system to support building and running C++ tests for the MATLAB Interface. The MATLAB interface should have clear documentation detailing how to build and run the C++ tests on all platforms. This should include instructions for building with and without specifying a custom `GTEST_ROOT` value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARROW-13100) [MATLAB] Integrate GoogleTest with MATLAB Interface C++ Code
[
https://issues.apache.org/jira/browse/ARROW-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-13100:
-
Description:
The MATLAB Interface for Apache Arrow will call into C++ code via MEX functions
to interact with the Arrow C++ libraries.
All of the C++ APIs that will support the MATLAB Interface will require
corresponding C++ tests to go with them.
We would like to reuse the CMake GoogleTest integration code that has already
been authored in
[cpp/cmake_modules/ThirdpartyToolchain.cmake|https://github.com/apache/arrow/blob/master/cpp/cmake_modules/ThirdpartyToolchain.cmake]
to enable us to author and execute C++ tests for the MATLAB Interface.
We imagine supporting two kinds of GoogleTest integration workflows:
# A user provided
[GTEST_ROOT|https://cmake.org/cmake/help/latest/module/FindGTest.html] value to
pre-built Google-Test binaries (e.g. GoogleTest binaries that were built as
part of building the Arrow C++ libraries).
# Automatic fetching/building of GoogleTest using
[ExternalProject|https://cmake.org/cmake/help/latest/module/ExternalProject.html]
From what we can tell, we should be able to reuse the [build_dependency
macro|https://github.com/apache/arrow/blob/57ecc73e6153fea04e0ac0d13792ba0abb0dd779/cpp/cmake_modules/ThirdpartyToolchain.cmake#L137]
{{declared in ThirdpartyToolchain.cmake}} to do this.
was:
The MATLAB Interface for Apache Arrow will call into C++ code via MEX functions
to interact with the Arrow C++ libraries.
All of the C++ APIs that will support the MATLAB Interface will require
corresponding C++ tests to go with them.
We would like to reuse the CMake GoogleTest integration code that has already
been authored in
[{{cpp/cmake_modules/ThirdpartyToolchain.cmake|https://github.com/apache/arrow/blob/master/cpp/cmake_modules/ThirdpartyToolchain.cmake]}}
to enable us to author and execute C++ tests for the MATLAB Interface.
We imagine supporting two kinds of GoogleTest integration workflows:
# A user provided
[{{GTEST_ROOT|https://cmake.org/cmake/help/latest/module/FindGTest.html]}}
value to pre-built Google-Test binaries (e.g. GoogleTest binaries that were
built as part of building the Arrow C++ libraries).
# Automatic fetching/building of GoogleTest using
[ExternalProject|https://cmake.org/cmake/help/latest/module/ExternalProject.html]
From what we can tell, we should be able to reuse the {{}}[build_dependency
macro|https://github.com/apache/arrow/blob/57ecc73e6153fea04e0ac0d13792ba0abb0dd779/cpp/cmake_modules/ThirdpartyToolchain.cmake#L137]
declared in {{ThirdpartyToolchain.cmake}} to do this.
> [MATLAB] Integrate GoogleTest with MATLAB Interface C++ Code
>
>
> Key: ARROW-13100
> URL: https://issues.apache.org/jira/browse/ARROW-13100
> Project: Apache Arrow
> Issue Type: Task
> Components: MATLAB
>Reporter: Kevin Gurney
>Assignee: Kevin Gurney
>Priority: Minor
>
> The MATLAB Interface for Apache Arrow will call into C++ code via MEX
> functions to interact with the Arrow C++ libraries.
> All of the C++ APIs that will support the MATLAB Interface will require
> corresponding C++ tests to go with them.
> We would like to reuse the CMake GoogleTest integration code that has already
> been authored in
> [cpp/cmake_modules/ThirdpartyToolchain.cmake|https://github.com/apache/arrow/blob/master/cpp/cmake_modules/ThirdpartyToolchain.cmake]
> to enable us to author and execute C++ tests for the MATLAB Interface.
> We imagine supporting two kinds of GoogleTest integration workflows:
> # A user provided
> [GTEST_ROOT|https://cmake.org/cmake/help/latest/module/FindGTest.html] value
> to pre-built Google-Test binaries (e.g. GoogleTest binaries that were built
> as part of building the Arrow C++ libraries).
> # Automatic fetching/building of GoogleTest using
> [ExternalProject|https://cmake.org/cmake/help/latest/module/ExternalProject.html]
> From what we can tell, we should be able to reuse the [build_dependency
> macro|https://github.com/apache/arrow/blob/57ecc73e6153fea04e0ac0d13792ba0abb0dd779/cpp/cmake_modules/ThirdpartyToolchain.cmake#L137]
> {{declared in ThirdpartyToolchain.cmake}} to do this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARROW-13100) [MATLAB] Integrate GoogleTest with MATLAB Interface C++ Code
[
https://issues.apache.org/jira/browse/ARROW-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-13100:
-
Description:
The MATLAB Interface for Apache Arrow will call into C++ code via MEX functions
to interact with the Arrow C++ libraries.
All of the C++ APIs that will support the MATLAB Interface will require
corresponding C++ tests to go with them.
We would like to reuse the CMake GoogleTest integration code that has already
been authored in
[{{cpp/cmake_modules/ThirdpartyToolchain.cmake|https://github.com/apache/arrow/blob/master/cpp/cmake_modules/ThirdpartyToolchain.cmake]}}
to enable us to author and execute C++ tests for the MATLAB Interface.
We imagine supporting two kinds of GoogleTest integration workflows:
# A user provided
[{{GTEST_ROOT|https://cmake.org/cmake/help/latest/module/FindGTest.html]}}
value to pre-built Google-Test binaries (e.g. GoogleTest binaries that were
built as part of building the Arrow C++ libraries).
# Automatic fetching/building of GoogleTest using
[ExternalProject|https://cmake.org/cmake/help/latest/module/ExternalProject.html]
From what we can tell, we should be able to reuse the {{}}[build_dependency
macro|https://github.com/apache/arrow/blob/57ecc73e6153fea04e0ac0d13792ba0abb0dd779/cpp/cmake_modules/ThirdpartyToolchain.cmake#L137]
declared in {{ThirdpartyToolchain.cmake}} to do this.
was:
The MATLAB Interface for Apache Arrow will call into C++ code via MEX functions
to interact with the Arrow C++ libraries.
All of the C++ APIs that will support the MATLAB Interface will require
corresponding C++ tests to go with them.
We would like to reuse the CMake GoogleTest integration code that has already
been authored in {{cpp/cmake_modules/ThirdpartyToolchain.cmake}} to enable us
to author and execute C++ tests for the MATLAB Interface.
We imagine supporting two kinds of GoogleTest integration workflows:
# A user provided {{GTEST_ROOT}} value to pre-built Google-Test binaries (e.g.
GoogleTest binaries that were built as part of building the Arrow C++
libraries).
# Automatic fetching/building of GoogleTest using
[ExternalProject|https://cmake.org/cmake/help/latest/module/ExternalProject.html]
From what we can tell, we should be able to reuse the {{build_dependency}}
function declared in {{ThirdpartyToolchain.cmake}} to do this.
> [MATLAB] Integrate GoogleTest with MATLAB Interface C++ Code
>
>
> Key: ARROW-13100
> URL: https://issues.apache.org/jira/browse/ARROW-13100
> Project: Apache Arrow
> Issue Type: Task
> Components: MATLAB
>Reporter: Kevin Gurney
>Assignee: Kevin Gurney
>Priority: Minor
>
> The MATLAB Interface for Apache Arrow will call into C++ code via MEX
> functions to interact with the Arrow C++ libraries.
> All of the C++ APIs that will support the MATLAB Interface will require
> corresponding C++ tests to go with them.
> We would like to reuse the CMake GoogleTest integration code that has already
> been authored in
> [{{cpp/cmake_modules/ThirdpartyToolchain.cmake|https://github.com/apache/arrow/blob/master/cpp/cmake_modules/ThirdpartyToolchain.cmake]}}
> to enable us to author and execute C++ tests for the MATLAB Interface.
> We imagine supporting two kinds of GoogleTest integration workflows:
> # A user provided
> [{{GTEST_ROOT|https://cmake.org/cmake/help/latest/module/FindGTest.html]}}
> value to pre-built Google-Test binaries (e.g. GoogleTest binaries that were
> built as part of building the Arrow C++ libraries).
> # Automatic fetching/building of GoogleTest using
> [ExternalProject|https://cmake.org/cmake/help/latest/module/ExternalProject.html]
> From what we can tell, we should be able to reuse the {{}}[build_dependency
> macro|https://github.com/apache/arrow/blob/57ecc73e6153fea04e0ac0d13792ba0abb0dd779/cpp/cmake_modules/ThirdpartyToolchain.cmake#L137]
> declared in {{ThirdpartyToolchain.cmake}} to do this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (ARROW-13100) [MATLAB] Integrate GoogleTest with MATLAB Interface C++ Code
[
https://issues.apache.org/jira/browse/ARROW-13100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Gurney updated ARROW-13100:
-
Description:
The MATLAB Interface for Apache Arrow will call into C++ code via MEX functions
to interact with the Arrow C++ libraries.
All of the C++ APIs that will support the MATLAB Interface will require
corresponding C++ tests to go with them.
We would like to reuse the CMake GoogleTest integration code that has already
been authored in {{cpp/cmake_modules/ThirdpartyToolchain.cmake}} to enable us
to author and execute C++ tests for the MATLAB Interface.
We imagine supporting two kinds of GoogleTest integration workflows:
# A user provided {{GTEST_ROOT}} value to pre-built Google-Test binaries (e.g.
GoogleTest binaries that were built as part of building the Arrow C++
libraries).
# Automatic fetching/building of GoogleTest using
[ExternalProject|https://cmake.org/cmake/help/latest/module/ExternalProject.html]
From what we can tell, we should be able to reuse the {{build_dependency}}
function declared in {{ThirdpartyToolchain.cmake}} to do this.
was:
The MATLAB Interface for Apache Arrow will call into C++ code via MEX functions
to interact with the Arrow C++ libraries.
All of the C++ APIs that will support the MATLAB Interface will require
corresponding C++ tests to go with them.
We would like to reuse the CMake GoogleTest integration code that has already
been authored in {{cpp/cmake_modules/ThirdpartyToolchain.cmake}} to enable us
to author and execute C++ tests for the MATLAB Interface.
We imagine supporting two kinds of GoogleTest integration workflows:
# A user provided {{GTEST_ROOT}} value to pre-built Google-Test binaries (e.g.
GoogleTest binaries that were built as part of building the Arrow C++
libraries).
# Automatic fetching/building of GoogleTest using [ExternalProject|
[https://cmake.org/cmake/help/latest/module/ExternalProject.html].] From what
we can tell, we should be able to reuse the {{build_dependency}} function
declared in {{ThirdpartyToolchain.cmake}} to do this.
> [MATLAB] Integrate GoogleTest with MATLAB Interface C++ Code
>
>
> Key: ARROW-13100
> URL: https://issues.apache.org/jira/browse/ARROW-13100
> Project: Apache Arrow
> Issue Type: Task
> Components: MATLAB
>Reporter: Kevin Gurney
>Assignee: Kevin Gurney
>Priority: Minor
>
> The MATLAB Interface for Apache Arrow will call into C++ code via MEX
> functions to interact with the Arrow C++ libraries.
> All of the C++ APIs that will support the MATLAB Interface will require
> corresponding C++ tests to go with them.
> We would like to reuse the CMake GoogleTest integration code that has already
> been authored in {{cpp/cmake_modules/ThirdpartyToolchain.cmake}} to enable us
> to author and execute C++ tests for the MATLAB Interface.
> We imagine supporting two kinds of GoogleTest integration workflows:
> # A user provided {{GTEST_ROOT}} value to pre-built Google-Test binaries
> (e.g. GoogleTest binaries that were built as part of building the Arrow C++
> libraries).
> # Automatic fetching/building of GoogleTest using
> [ExternalProject|https://cmake.org/cmake/help/latest/module/ExternalProject.html]
> From what we can tell, we should be able to reuse the {{build_dependency}}
> function declared in {{ThirdpartyToolchain.cmake}} to do this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (ARROW-13100) [MATLAB] Integrate GoogleTest with MATLAB Interface C++ Code
Kevin Gurney created ARROW-13100:
Summary: [MATLAB] Integrate GoogleTest with MATLAB Interface C++
Code
Key: ARROW-13100
URL: https://issues.apache.org/jira/browse/ARROW-13100
Project: Apache Arrow
Issue Type: Task
Components: MATLAB
Reporter: Kevin Gurney
Assignee: Kevin Gurney
The MATLAB Interface for Apache Arrow will call into C++ code via MEX functions
to interact with the Arrow C++ libraries.
All of the C++ APIs that will support the MATLAB Interface will require
corresponding C++ tests to go with them.
We would like to reuse the CMake GoogleTest integration code that has already
been authored in {{cpp/cmake_modules/ThirdpartyToolchain.cmake}} to enable us
to author and execute C++ tests for the MATLAB Interface.
We imagine supporting two kinds of GoogleTest integration workflows:
# A user provided {{GTEST_ROOT}} value to pre-built Google-Test binaries (e.g.
GoogleTest binaries that were built as part of building the Arrow C++
libraries).
# Automatic fetching/building of GoogleTest using [ExternalProject|
[https://cmake.org/cmake/help/latest/module/ExternalProject.html].] From what
we can tell, we should be able to reuse the {{build_dependency}} function
declared in {{ThirdpartyToolchain.cmake}} to do this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
