jorgecarleitao commented on a change in pull request #107:
URL: https://github.com/apache/arrow-site/pull/107#discussion_r622258786
##########
File path: _posts/2021-04-27-rust-dev-workflow.md
##########
@@ -0,0 +1,80 @@
+---
+layout: post
+title: "A New Development Workflow for Arrow's Rust Implementation"
+date: "2021-04-27 00:00:00"
+author: ruanpa
+categories: [application]
+---
+<!--
+{% comment %}
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+{% endcomment %}
+-->
+
+The Apache Arrow Rust community is excited to announce that its migration to a
new development workflow is now complete! If you're considering Rust as a
language for working with columnar data, read on and see how your use case
might benefit from our new and improved project setup.
+
+In recent months, members of the community have been working closely with
Arrow's [Project Management Committee][1] and other contributors to expand the
set of available workflows for Arrow implementations. The goal was to define a
new development process that ultimately:
+- Enables a faster release cadence that adheres to [SemVer][15] where
appropriate
+- Encourages maximum participation from the wider community with unified
tooling
+- Ensures that we continue to uphold the tenets of [The Apache Way][2]
+
+If you're just here for the highlights, the major outcomes of these
discussions are as follows:
+- The Rust projects have moved to separate repositories, outside the main
Arrow [monorepo][9]
+ - [arrow-rs][7] for the core Arrow implementation in Rust
Review comment:
```suggestion
- [arrow-rs][7] for the Arrow, arrow flight, and parquet implementation
in Rust
```
##########
File path: _posts/2021-04-27-rust-dev-workflow.md
##########
@@ -0,0 +1,80 @@
+---
+layout: post
+title: "A New Development Workflow for Arrow's Rust Implementation"
+date: "2021-04-27 00:00:00"
+author: ruanpa
+categories: [application]
+---
+<!--
+{% comment %}
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+{% endcomment %}
+-->
+
+The Apache Arrow Rust community is excited to announce that its migration to a
new development workflow is now complete! If you're considering Rust as a
language for working with columnar data, read on and see how your use case
might benefit from our new and improved project setup.
+
+In recent months, members of the community have been working closely with
Arrow's [Project Management Committee][1] and other contributors to expand the
set of available workflows for Arrow implementations. The goal was to define a
new development process that ultimately:
+- Enables a faster release cadence that adheres to [SemVer][15] where
appropriate
+- Encourages maximum participation from the wider community with unified
tooling
+- Ensures that we continue to uphold the tenets of [The Apache Way][2]
+
+If you're just here for the highlights, the major outcomes of these
discussions are as follows:
+- The Rust projects have moved to separate repositories, outside the main
Arrow [monorepo][9]
Review comment:
I would
```suggestion
- The Rust projects have moved from the [main arrow repository][9] to
separate repositories
```
##########
File path: _posts/2021-04-27-rust-dev-workflow.md
##########
@@ -0,0 +1,80 @@
+---
+layout: post
+title: "A New Development Workflow for Arrow's Rust Implementation"
+date: "2021-04-27 00:00:00"
+author: ruanpa
+categories: [application]
+---
+<!--
+{% comment %}
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+{% endcomment %}
+-->
+
+The Apache Arrow Rust community is excited to announce that its migration to a
new development workflow is now complete! If you're considering Rust as a
language for working with columnar data, read on and see how your use case
might benefit from our new and improved project setup.
+
+In recent months, members of the community have been working closely with
Arrow's [Project Management Committee][1] and other contributors to expand the
set of available workflows for Arrow implementations. The goal was to define a
new development process that ultimately:
+- Enables a faster release cadence that adheres to [SemVer][15] where
appropriate
+- Encourages maximum participation from the wider community with unified
tooling
+- Ensures that we continue to uphold the tenets of [The Apache Way][2]
+
+If you're just here for the highlights, the major outcomes of these
discussions are as follows:
+- The Rust projects have moved to separate repositories, outside the main
Arrow [monorepo][9]
+ - [arrow-rs][7] for the core Arrow implementation in Rust
+ - [arrow-datafusion][8] for DataFusion and Ballista (more on these
projects below!)
+- The Rust community will use GitHub Issues for tracking feature development
and issues, replacing the Jira instance maintained by the Apache Software
Foundation (ASF)
+
+But why, as a community, have we decided to change our processes? Let's take a
slightly more in-depth look at the Rust implementation's needs.
+
+## Project Structure
+The Rust implementation of Arrow actually consists of several distinct
projects, or in Rust parlance, ["crates"][3]. In addition to the Arrow crate
that contains core functionality such as the in-memory format and inter-process
communication, we also maintain:
+- [DataFusion][4]: an extensible in-memory query execution engine using Arrow
as its format
+- [Ballista][5]: a distributed compute platform, powered by Apache Arrow and
DataFusion
Review comment:
We have more than 3 crates; within `arrow-rs` we have 4 or 5. This split
is more related to the nature of these crates (AFAIK).
##########
File path: _posts/2021-04-27-rust-dev-workflow.md
##########
@@ -0,0 +1,80 @@
+---
+layout: post
+title: "A New Development Workflow for Arrow's Rust Implementation"
+date: "2021-04-27 00:00:00"
+author: ruanpa
+categories: [application]
+---
+<!--
+{% comment %}
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+{% endcomment %}
+-->
+
+The Apache Arrow Rust community is excited to announce that its migration to a
new development workflow is now complete! If you're considering Rust as a
language for working with columnar data, read on and see how your use case
might benefit from our new and improved project setup.
+
+In recent months, members of the community have been working closely with
Arrow's [Project Management Committee][1] and other contributors to expand the
set of available workflows for Arrow implementations. The goal was to define a
new development process that ultimately:
+- Enables a faster release cadence that adheres to [SemVer][15] where
appropriate
+- Encourages maximum participation from the wider community with unified
tooling
+- Ensures that we continue to uphold the tenets of [The Apache Way][2]
+
+If you're just here for the highlights, the major outcomes of these
discussions are as follows:
+- The Rust projects have moved to separate repositories, outside the main
Arrow [monorepo][9]
+ - [arrow-rs][7] for the core Arrow implementation in Rust
+ - [arrow-datafusion][8] for DataFusion and Ballista (more on these
projects below!)
+- The Rust community will use GitHub Issues for tracking feature development
and issues, replacing the Jira instance maintained by the Apache Software
Foundation (ASF)
Review comment:
I would add a third bullet: that the release cycles are independent. IMO
that is what enables `SemVer`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
