[jira] [Updated] (ARROW-14218) [R] More improvements to developer docs
[ https://issues.apache.org/jira/browse/ARROW-14218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Keane updated ARROW-14218: --- Fix Version/s: (was: 9.0.0) > [R] More improvements to developer docs > --- > > Key: ARROW-14218 > URL: https://issues.apache.org/jira/browse/ARROW-14218 > Project: Apache Arrow > Issue Type: Improvement > Components: R >Reporter: Nicola Crane >Priority: Major > > * Add link to the main contributions guidelines > * Add a test of "how I know that my dev setup is OK?" to the end of the > R-only step > * The R-only instructions just have instructions on how to install libarrow > but we should add a little about how to connect it up with the repo clone; > the instructions mention it in the Linux version but could be more explicit > * When a user clones the repo via RStudio it creates an .rproj file in the > root directory - we should add an instructions to clone the arrow fork from > the command line so we can use the project's .rproj file > * We should consider removing the instruction for installing the released > version of libarrow (or demoting it to the second place and explain why we'd > use it) as typically a dev would want the dev version > * Mac - you can't just install openssl, you need to add it to your path as > LibreSSL is the default - we should add instructions about this > * Better demarcation between "special instructions for Linux" and the next > section - maybe use tabs again? > * clarification of the difference between the build directory and the > installation directory -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARROW-14218) [R] More improvements to developer docs
[ https://issues.apache.org/jira/browse/ARROW-14218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raúl Cumplido updated ARROW-14218: -- Fix Version/s: 9.0.0 (was: 8.0.0) > [R] More improvements to developer docs > --- > > Key: ARROW-14218 > URL: https://issues.apache.org/jira/browse/ARROW-14218 > Project: Apache Arrow > Issue Type: Improvement > Components: R >Reporter: Nicola Crane >Priority: Major > Fix For: 9.0.0 > > > * Add link to the main contributions guidelines > * Add a test of "how I know that my dev setup is OK?" to the end of the > R-only step > * The R-only instructions just have instructions on how to install libarrow > but we should add a little about how to connect it up with the repo clone; > the instructions mention it in the Linux version but could be more explicit > * When a user clones the repo via RStudio it creates an .rproj file in the > root directory - we should add an instructions to clone the arrow fork from > the command line so we can use the project's .rproj file > * We should consider removing the instruction for installing the released > version of libarrow (or demoting it to the second place and explain why we'd > use it) as typically a dev would want the dev version > * Mac - you can't just install openssl, you need to add it to your path as > LibreSSL is the default - we should add instructions about this > * Better demarcation between "special instructions for Linux" and the next > section - maybe use tabs again? > * clarification of the difference between the build directory and the > installation directory -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (ARROW-14218) [R] More improvements to developer docs
[ https://issues.apache.org/jira/browse/ARROW-14218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Keane updated ARROW-14218: --- Fix Version/s: 8.0.0 (was: 7.0.0) > [R] More improvements to developer docs > --- > > Key: ARROW-14218 > URL: https://issues.apache.org/jira/browse/ARROW-14218 > Project: Apache Arrow > Issue Type: Improvement > Components: R >Reporter: Nicola Crane >Priority: Major > Fix For: 8.0.0 > > > * Add link to the main contributions guidelines > * Add a test of "how I know that my dev setup is OK?" to the end of the > R-only step > * The R-only instructions just have instructions on how to install libarrow > but we should add a little about how to connect it up with the repo clone; > the instructions mention it in the Linux version but could be more explicit > * When a user clones the repo via RStudio it creates an .rproj file in the > root directory - we should add an instructions to clone the arrow fork from > the command line so we can use the project's .rproj file > * We should consider removing the instruction for installing the released > version of libarrow (or demoting it to the second place and explain why we'd > use it) as typically a dev would want the dev version > * Mac - you can't just install openssl, you need to add it to your path as > LibreSSL is the default - we should add instructions about this > * Better demarcation between "special instructions for Linux" and the next > section - maybe use tabs again? > * clarification of the difference between the build directory and the > installation directory -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (ARROW-14218) [R] More improvements to developer docs
[ https://issues.apache.org/jira/browse/ARROW-14218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Crane updated ARROW-14218: - Description: * Add link to the main contributions guidelines * Add a test of "how I know that my dev setup is OK?" to the end of the R-only step * The R-only instructions just have instructions on how to install libarrow but we should add a little about how to connect it up with the repo clone; the instructions mention it in the Linux version but could be more explicit * When a user clones the repo via RStudio it creates an .rproj file in the root directory - we should add an instructions to clone the arrow fork from the command line so we can use the project's .rproj file * We should consider removing the instruction for installing the released version of libarrow (or demoting it to the second place and explain why we'd use it) as typically a dev would want the dev version * Mac - you can't just install openssl, you need to add it to your path as LibreSSL is the default - we should add instructions about this * Better demarcation between "special instructions for Linux" and the next section - maybe use tabs again? * clarification of the difference between the build directory and the installation directory was: * Add link to the main contributions guidelines * Add a test of "how I know that my dev setup is OK?" to the end of the R-only step * The R-only instructions just have instructions on how to install libarrow but we should add a little about how to connect it up with the repo clone; the instructions mention it in the Linux version but could be more explicit * When a user clones the repo via RStudio it creates an .rproj file in the root directory - we should add an instructions to clone the arrow fork from the command line so we can use the project's .rproj file * We should consider removing the instruction for installing the released version of libarrow (or demoting it to the second place and explain why we'd use it) as typically a dev would want the dev version * Mac - you can't just install openssl, you need to add it to your path as LibreSSL is the default - we should add instructions about this * Better demarcation between "special instructions for Linux" and the next section - maybe use tabs again? > [R] More improvements to developer docs > --- > > Key: ARROW-14218 > URL: https://issues.apache.org/jira/browse/ARROW-14218 > Project: Apache Arrow > Issue Type: Improvement > Components: R >Reporter: Nicola Crane >Priority: Major > Fix For: 7.0.0 > > > * Add link to the main contributions guidelines > * Add a test of "how I know that my dev setup is OK?" to the end of the > R-only step > * The R-only instructions just have instructions on how to install libarrow > but we should add a little about how to connect it up with the repo clone; > the instructions mention it in the Linux version but could be more explicit > * When a user clones the repo via RStudio it creates an .rproj file in the > root directory - we should add an instructions to clone the arrow fork from > the command line so we can use the project's .rproj file > * We should consider removing the instruction for installing the released > version of libarrow (or demoting it to the second place and explain why we'd > use it) as typically a dev would want the dev version > * Mac - you can't just install openssl, you need to add it to your path as > LibreSSL is the default - we should add instructions about this > * Better demarcation between "special instructions for Linux" and the next > section - maybe use tabs again? > * clarification of the difference between the build directory and the > installation directory -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARROW-14218) [R] More improvements to developer docs
[ https://issues.apache.org/jira/browse/ARROW-14218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Crane updated ARROW-14218: - Description: * Add link to the main contributions guidelines * Add a test of "how I know that my dev setup is OK?" to the end of the R-only step * The R-only instructions just have instructions on how to install libarrow but we should add a little about how to connect it up with the repo clone; the instructions mention it in the Linux version but could be more explicit * When a user clones the repo via RStudio it creates an .rproj file in the root directory - we should add an instructions to clone the arrow fork from the command line so we can use the project's .rproj file * We should consider removing the instruction for installing the released version of libarrow (or demoting it to the second place and explain why we'd use it) as typically a dev would want the dev version * Mac - you can't just install openssl, you need to add it to your path as LibreSSL is the default - we should add instructions about this * Better demarcation between "special instructions for Linux" and the next section - maybe use tabs again? was: * Add link to the main contributions guidelines * Add a test of "how I know that my dev setup is OK?" to the end of the R-only step * The R-only instructions just have instructions on how to install libarrow but we should add a little about how to connect it up with the repo clone; the instructions mention it in the Linux version but could be more explicit * When a user clones the repo via RStudio it creates an .rproj file in the root directory - we should add an instructions to clone the arrow fork from the command line so we can use the project's .rproj file * We should consider removing the instruction for installing the released version of libarrow (or demoting it to the second place and explain why we'd use it) as typically a dev would want the dev version * Mac - you can't just install openssl, you need to add it to your path as LibreSSL is the default - we should add instructions about this * Better demarcation between "special instructions for Linux" and the next section > [R] More improvements to developer docs > --- > > Key: ARROW-14218 > URL: https://issues.apache.org/jira/browse/ARROW-14218 > Project: Apache Arrow > Issue Type: Improvement > Components: R >Reporter: Nicola Crane >Priority: Major > Fix For: 7.0.0 > > > * Add link to the main contributions guidelines > * Add a test of "how I know that my dev setup is OK?" to the end of the > R-only step > * The R-only instructions just have instructions on how to install libarrow > but we should add a little about how to connect it up with the repo clone; > the instructions mention it in the Linux version but could be more explicit > * When a user clones the repo via RStudio it creates an .rproj file in the > root directory - we should add an instructions to clone the arrow fork from > the command line so we can use the project's .rproj file > * We should consider removing the instruction for installing the released > version of libarrow (or demoting it to the second place and explain why we'd > use it) as typically a dev would want the dev version > * Mac - you can't just install openssl, you need to add it to your path as > LibreSSL is the default - we should add instructions about this > * Better demarcation between "special instructions for Linux" and the next > section - maybe use tabs again? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ARROW-14218) [R] More improvements to developer docs
[ https://issues.apache.org/jira/browse/ARROW-14218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicola Crane updated ARROW-14218: - Description: * Add link to the main contributions guidelines * Add a test of "how I know that my dev setup is OK?" to the end of the R-only step * The R-only instructions just have instructions on how to install libarrow but we should add a little about how to connect it up with the repo clone; the instructions mention it in the Linux version but could be more explicit * When a user clones the repo via RStudio it creates an .rproj file in the root directory - we should add an instructions to clone the arrow fork from the command line so we can use the project's .rproj file * We should consider removing the instruction for installing the released version of libarrow (or demoting it to the second place and explain why we'd use it) as typically a dev would want the dev version * Mac - you can't just install openssl, you need to add it to your path as LibreSSL is the default - we should add instructions about this * Better demarcation between "special instructions for Linux" and the next section was: * Add link to the main contributions guidelines * Add a test of "how I know that my dev setup is OK?" to the end of the R-only step * The R-only instructions just have instructions on how to install libarrow but we should add a little about how to connect it up with the repo clone; the instructions mention it in the Linux version but could be more explicit * When a user clones the repo via RStudio it creates an .rproj file in the root directory - we should add an instructions to clone the arrow fork from the command line so we can use the project's .rproj file * We should consider removing the instruction for installing the released version of libarrow (or demoting it to the second place and explain why we'd use it) as typically a dev would want the dev version > [R] More improvements to developer docs > --- > > Key: ARROW-14218 > URL: https://issues.apache.org/jira/browse/ARROW-14218 > Project: Apache Arrow > Issue Type: Improvement > Components: R >Reporter: Nicola Crane >Priority: Major > Fix For: 7.0.0 > > > * Add link to the main contributions guidelines > * Add a test of "how I know that my dev setup is OK?" to the end of the > R-only step > * The R-only instructions just have instructions on how to install libarrow > but we should add a little about how to connect it up with the repo clone; > the instructions mention it in the Linux version but could be more explicit > * When a user clones the repo via RStudio it creates an .rproj file in the > root directory - we should add an instructions to clone the arrow fork from > the command line so we can use the project's .rproj file > * We should consider removing the instruction for installing the released > version of libarrow (or demoting it to the second place and explain why we'd > use it) as typically a dev would want the dev version > * Mac - you can't just install openssl, you need to add it to your path as > LibreSSL is the default - we should add instructions about this > * Better demarcation between "special instructions for Linux" and the next > section -- This message was sent by Atlassian Jira (v8.3.4#803005)
