Thanks for the feedback Steve! > * the ability cross reference stuff from other jira projects > * the simplicity of being able to use a string like "PARQUET-123" to refer to an issue > * the ease of being able to set up your ide and web browser to go from a reference like this to a jira page > * maybe uber-JIRAs
Speaking from the experience after Arrow's migration: - Automated linking with other ASF Jira projects will indeed be lost. But as you note automated linking with GitHub PRs and other GitHub issue trackers will be gained. - I do miss the "ARROW-123" issue naming convention on channels other than GitHub. GitHub does automatically rename links to its own namespace e.g.: "apache/parquet-java#123". See [1]. - Not sure how much effort that would take with GitHub, but given its market share it shouldn't be much more than on Jira? - GitHub issues can be linked with markdown to-do lists [2] or they can be linked into projects with various views. > Assuming it goes ahead, it'd be good to know how best other projects > managed the transition and what worked/didn't, in particular "is there > anything which needs to be done before/during the move to make the move > easier" Arrow discussed migration requirements here [2] and we then executed this script [4]. 18k tickets were migrated [5] and ARROW Jira was put into read-only mode. Judging from that experience I would suggest now is a good time to bulk labels to tickets if we know that we want to add some that are currently not being used in Jira. Another thing to note: we'll be starting with an empty GitHub issue tracker. If say we're missing a label or milestones we can easily scrap the initial copy and reimport corrected issues before we lock Jira and start using GitHub. Assuming we don't veto the vote at this point I can run the migrations on Friday. [1] https://github.com/apache/arrow/issues/42157#issuecomment-2169171974 [2] https://github.com/apache/arrow/issues/14542 [3] https://github.com/orgs/apache/projects/289 [4] https://github.com/rok/arrow-migration/blob/main/move_jira_issues_to_github.ipynb [5] https://github.com/apache/arrow/issues?q=is%3Aissue+author%3Aasfimport Rok On Mon, Jun 17, 2024 at 4:38 PM Steve Loughran <ste...@cloudera.com.invalid> wrote: > =0 > > I'm going to miss > * the ability cross reference stuff from other jira projects > * the simplicity of being able to use a string like "PARQUET-123" to refer > to an issue > * the ease of being able to set up your ide and web browser to go from a > reference like this to a jira page > * maybe uber-JIRAs > > In its favour: > * JIRA has long abandoned the needs of developers which can be seen by the > addition of features like PDF rendering and voice recognition and > supporting an explosion of dashboards for every software development > processes have long destroyed the notion of "agile" > * while foundational over things which would be useful such as "don't > remove the link to a newly created issue after 15 seconds" > * JIRA's public API is notoriously brittle, whereas github has an api, and > in "gh" an official command line tool to work with them. Great for cutting > releases too. > * github issues integrate better with github prs. > > Assuming it goes ahead, it'd be good to know how best other projects > managed the transition and what worked/didn't, in particular "is there > anything which needs to be done before/during the move to make the move > easier" > > On Thu, 13 Jun 2024 at 19:14, Rok Mihevc <rok.mih...@gmail.com> wrote: > > > Hi all, > > > > Following the ML discussion [1] I would like to propose a vote for > > parquet-java, parquet-format, parquet-testing and parquet-site issues to > be > > moved from Parquet Jira [2] to respective GitHub issue trackers. If the > > vote passes parquet-format, parquet-java and parquet-testing issue > trackers > > will be enabled (see [3], [4], [5]) and issues migrated based on their > > respective component. > > > > [1] https://lists.apache.org/thread/sc9zoxd3pd10odtgbrsh5qh7szhl2lhg > > [2] https://issues.apache.org/jira/projects/PARQUET/issues/ > > [3] https://github.com/apache/parquet-format/pull/255 > > [4] https://github.com/apache/parquet-java/pull/1362 > > [5] https://github.com/apache/parquet-testing/pull/50 > > > > The vote will be open for at least 72 hours. > > > > [ ] +1 Migrate parquet issues > > [ ] +0 > > [ ] -1 Do not migrate parquet issues because... > > > > > > Rok > > >
