运行时系统中的问题管理特征分析
Characterizing Issue Management in Runtime Systems
AI总结:
本文对GitHub中34个运行时系统存储库的约118K个问题进行了实证研究,揭示了问题类型、解决率及特征对问题关闭的影响,并提出了六项改进建议。
摘要:
像Java这样的现代编程语言需要运行时系统来支持软件应用程序在多种计算平台和操作系统上的实现与部署。这些运行时系统通常在GitHub托管的存储库中开发,基于大型软件公司(如IBM、Microsoft)与OSS开发者之间的密切合作。然而,尽管它们很受欢迎且被广泛使用;据我们所知,这些存储库从未被研究过。我们报告了一项关于GitHub中34个运行时系统存储库的约118K个问题的实证研究。我们发现,关于增强、测试失败和bug的问题大多发布在运行时系统存储库上,而与解决方案相关的讨论大多出现在问题讨论中。运行时系统存储库中82.69%的问题已解决,0.69%的问题被忽略;这些存储库中的问题关闭率、忽略率和处理时间的中位数分别为76.1%、2.2%和58天。82.65%的问题被标记了标签,而只有28.30%的问题有指定的负责人,90.65%的问题包含至少一条评论;此外,问题报告中这些特征的存在也会影响问题的关闭。基于这些发现,我们提供了六项建议。
英文摘要:
Modern programming languages like Java require runtime systems to support the implementation and deployment of software applications in diverse computing platforms and operating systems. These runtime systems are normally developed in GitHub-hosted repositories based on close collaboration between large software companies (e.g., IBM, Microsoft) and OSS developers. However, despite their popularity and broad usage; to the best of our knowledge, these repositories have never been studied. We report an empirical study of around 118K issues from 34 runtime system repos in GitHub. We found that issues regarding enhancement, test failure and bug are mostly posted on runtime system repositories and solution related discussion are mostly present on issue discussion. 82.69% issues in the runtime system repositories have been resolved and 0.69% issues are ignored; median of issue close rate, ignore rate and addressing time in these repositories are 76.1%, 2.2% and 58 days respectively. 82.65% issues are tagged with labels while only 28.30% issues have designated assignees and 90.65% issues contain at least one comment; also presence of these features in an issue report can affect issue closure. Based on the findings, we offer six recommendat
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。