Open nealrichardson opened 1 year ago
Would love to get rid of all of that but we still have ~5 PARQUET issues per release from JIRA. IMO we should just get rid of that too, I think most of the parquet issues are handled within arrow Jira/GH anyway...
Would love to get rid of all of that but we still have ~5 PARQUET issues per release from JIRA. IMO we should just get rid of that too, I think most of the parquet issues are handled within arrow Jira/GH anyway...
IIUC the Parquet PMC would have to be ok with moving the parquet-cpp issue tracking to apache/arrow/issues
. I don't know why there would be objection, particularly since the code has lived in arrow for years now, but technically they are responsible, governance-wise.
Maybe @pitrou can start a lazy consensus thread on the parquet mailing list about that?
I'd be happy to do the migration.
A mere lazy consensus wouldn't be enough as it's a disruptive change. It would need an actual PMC vote. Given the lack of reaction on the previous ML thread, I'm not optimistic.
We can revive this now that Parquet also uses GH for issues. @raulcd
Describe the enhancement requested
Since we've migrated, we can drop all of that, right? Also include the jira token store in
dev/merge.conf.sample
.Component(s)
Developer Tools