Hello, As a quick update on the issue tracking migration:
- Basic extract from Jira and conversion/import to GitHub issues works well. Some tweaking is needed around content. - Updating source Jira issues now works [1] - The biggest outstanding issue is how to represent related issues [2] - Issue attachment migration hasn't been implemented yet [3] - I plan to execute a test migration to a throw-away personal repo this weekend. I will avoid mentioning users or updating the source Jira issues. - I've previously exported all Jira issues and converted to GitHub issue JSON format, but did not import the results. The export and conversion took about 3h to complete. [1] https://issues.apache.org/jira/browse/ARROW-18308 [2] https://github.com/apache/arrow/issues/14520#issuecomment-1311118773 [3] https://github.com/apache/arrow/issues/14513 Thanks, Todd On Wed, Nov 9, 2022 at 4:40 PM Ian Cook <i...@ursacomputing.com> wrote: > Attendees: > > - Ian Cook > - Raúl Cumplido > - Bin Deng > - Sean Gallagher > - Will Jones > - David Li > - Ashish Paliwal > - Niranda Perera > - Matthew Topol > > > Discussion: > > 10.0.1 release > > - Primary reason for this patch release is that we do not have PyArrow > 10.0.0 wheels for Python 3.11, because the Arrow 10.0.0 and Python > 3.11 releases were very close in time. > - Our CI and nightly test matrix does not currently include > environments with Python 3.11. We want to add Python 3.11 this matrix > and see that all tests are passing before we do the 10.0.1 release. > - In the meantime, users of Python 3.11 can use the latest nightly > builds which include Python 3.11 wheels. This was implemented in [1]. > Installation instructions are at [2]. > - We also want to include some fixes for other Arrow libraries > including Go and Java in the 10.0.1 release > - We do not yet have an estimated time for the release. The release > manager has not yet been determined. > > Migrating issue reporting from Jira to GitHub > > - As described at [3]: "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 set of GitHub issues to capture outstanding > questions and tasks associated with the Jira --> GitHub Issues > migration [4] > - We will also need to modify the PR merge script, release automation > scripts, Archery and Crossbow code, etc. as a part of this migration. > These are not all captured in the GitHub issues above. > - The November 6 date has passed, but the ASF Jira account signup page > seems to still be available. > - If the migration to GitHub Issues is not expected to be complete > until weeks after Jira account signup has closed, what should we do in > the interim? Should we (a) ask new participants to use GitHub issues > for their reports, or (b) offer to create Jira accounts for new > participants? Input on this question is welcome. > > [1] https://github.com/apache/arrow/pull/14499 > [2] > https://arrow.apache.org/docs/developers/python.html#installing-nightly-packages > [3] https://lists.apache.org/thread/l545m95xmf3w47oxwqxvg811or7b93tb > [4] > https://github.com/apache/arrow/issues?q=is%3Aissue+is%3Aopen+MIGRATION > > On Wed, Nov 9, 2022 at 9:01 AM Ian Cook <i...@ursacomputing.com> wrote: > > > > Hi all, > > > > Our biweekly sync call is today at 12:00 noon Eastern time. > > > > The Zoom meeting URL for this and other biweekly Arrow sync calls is: > > https://zoom.us/j/87649033008?pwd=SitsRHluQStlREM0TjJVYkRibVZsUT09 > > > > Alternatively, enter this information into the Zoom website or app to > > join the call: > > Meeting ID: 876 4903 3008 > > Passcode: 958092 > > > > Thanks, > > Ian >
