Hi, I just wanted to add that with the recent migration to GitHub issues for Arrow we have updated our development tools (merge script, archery release tasks, ...) to work with GitHub but we haven't been able to drop JIRA support due to having to support Parquet issues. This makes us have to support two issue trackers at the moment. For context on the 11.0.0 release there were 6 issues tracked on the JIRA Parquet.
Thanks, Raúl El jue, 2 feb 2023 a las 10:14, Antoine Pitrou (<anto...@python.org>) escribió: > > Hi Will, > > Le 01/02/2023 à 20:27, Will Jones a écrit : > > > > First, it's not obvious where issues are supposed to be open: In Parquet > > Jira or Arrow GitHub issues. Looking back at some of the original > > discussion, it looks like the intention was > > > > * use PARQUET-XXX for issues relating to Parquet core > >> * use ARROW-XXX for issues relation to Arrow's consumption of Parquet > >> core (e.g. changes that are in parquet/arrow right now) > >> > > The README for the old parquet-cpp repo [3] states instead in it's > > migration note: > > > > JIRA issues should continue to be opened in the PARQUET JIRA project. > > > > Either way, it doesn't seem like this process is obvious to people. > Perhaps > > we could clarify this and add notices to Arrow's GitHub issues template? > > I agree we should clarify this. I have no personal preference, but I > will note that Github issues decrease friction as having a GH account is > already necessary for submitting PRs. > > > Second, committer status is a little unclear. I am a committer on Arrow, > > but not on Parquet right now. Does that mean I should only merge Parquet > > C++ PRs for code changes in parquet/arrow? Or that I shouldn't merge > > Parquet changes at all? > > Since Parquet C++ is part of Arrow C++, you are allowed to merge Parquet > C++ changes. As always you should ensure you have sufficient > understanding of the contribution, and that it follows established > practices: > https://arrow.apache.org/docs/dev/developers/reviewing.html > > > Also, are the contributions to Arrow C++ Parquet being actively reviewed > > for potential new committers? > > I would certainly do. > > Regards > > Antoine. >
