m/document/d/1UaSJs-oyuq8QvlUPoQ9GeiwP19LK5ZzF_5-HLfHDCIg/edit?usp=sharing
Todd Farmer
"ASF Infra has announced that, due to spam
> account creation, it will no longer be possible for people to sign
> themselves up for a Jira account to report issues as of November 6.
> Instead, the PMC will have to request the creation of Jira accounts."
> - Todd Farmer created a se
I'm beginning to track decisions needing to be made and problems needing to
be solved in the Arrow project GitHub issues, prefixing all such issues
with "MIGRATION: ..". They can be found here:
https://github.com/apache/arrow/issues?q=is%3Aissue+is%3Aopen+MIGRATION
I feel this will be a better fo
Hi,
I've been working through a proof-of-concept migration, moving specific
ARROW issues into a personal test repo on GitHub. I've made this repo
public to help demonstrate limitations, successes and options as we
consider this further:
https://github.com/toddfarmer/test_import/issues?q=is%3Aissu
I can't claim experience migrating to GitHub issues, but I've done some
work with Jira APIs and import/export tools. I'm happy to help draft a
proposal or proof-of-concept to validate if nobody else expresses interest,
or to assist anybody who does.
Todd
On Sat, Oct 22, 2022 at 12:08 PM Neal Rich
Hi,
I've been thinking a lot about maintenance and lifecycle policies and
defect classification recently - I'm very grateful this is being raised. I
believe establishing such policies will prove instrumental to enable
adoption of Arrow for a number of use cases that prioritize stability over
innov
;
> > > > In svbeb7ncnnyn0p3yusdhrp6mvymf...@mail.gmail.com
> > >
> > > > "Proposal: Allow any ASF Jira user to assign ARROW issues" on Wed,
> 10
> > > > Aug 2022 14:32:21 -0600,
> > > > Todd Farmer wrote:
> >
Hello,
Community members seeking to address issues in the ASF Jira ARROW project
must both register for ASF Jira and be given the "Contributor" role.
Current project documentation [1] instructs individuals to request this
role via this mailing list, or in a comment on the issue itself. This adds
f
0it%20is%20no%20longer%20being%20actively%20worked.%22%20ORDER%20BY%20updated%20DESC
[2]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20ARROW%20AND%20resolution%20%3D%20Unresolved%20%20AND%20assignee%20IS%20NOT%20EMPTY%20AND%20updated%20%3C%20-90d
[3] https://github.com/apache/arrow/pull/
Hello,
Apologies for the late response to this thread. While not related to the
vote, I do have a related question about administration of releases such as
this. I notice:
1. There is no 8.0.1 release notes [1] - should this be added? It's worth
noting that no release notes currently reference AR
ated%20%3C%20-90d
[3] https://arrow.apache.org/docs/developers/bug_reports.html
Best regards,
Todd Farmer
11 matches
Mail list logo
