We recommend you first search among existing Github issues. The community may already address the same idea. If you could find the issue, you may want to contribute to the existing issue.
If you cannot find the same idea in the issues, you first need to write a GitHub issue (e.g. issues in Arrow-julia) for a bug fix or planned features for the improvement. To write an issue would help the community have visibility and opportunities for collaborations before a pull request (PR) shows up. This is for the Apache way. We can use GitHub labels to identify bugs.
It should not be necessary to file an issue for some non-code changes, such as CI changes or minor documentation updates such as fixing typos.
After writing the issue, you may want to write a code by creating a PR. In the PR, it is preferable to refer to the issue number (e.g. #1) that you already created.
We ask that all discussions about major changes in the codebase happen publicly on the arrow-dev mailing-list.
You can also ask on the mailing-list, see above.
When developing on Arrow.jl it is recommended that you run the following to ensure that any changes to ArrowTypes.jl are immediately available to Arrow.jl without requiring a release:
julia --project -e 'using Pkg; Pkg.develop(path="src/ArrowTypes")'
The Julia community would like an independent release cycle. Release for apache/arrow doesn‘t include the Julia implementation. The Julia implementation uses separated version scheme. (apache/arrow uses 6.0.0 as the next version but the next Julia implementation release doesn’t use 6.0.0.)