[ English | English (United Kingdom) | Deutsch | Indonesia | 中文 (简体, 中国) | español (México) | 한국어 (대한민국) ]

任务追踪

本节提供有关Storyboard和Launchpad任务跟踪器的信息。 您可以了解Storyboard事件和任务,看板和任务列表以及Launchpad蓝图和bug。

注解

本章节假设您已完成 帐户设置 指南。

本部分允许您:

  • 了解OpenStack用于任务管理的不同工具

  • 了解如何报告bug并提出功能

OpenStack使用什么任务跟踪器?

每个项目在报告bug和规划新功能的过程中都是不同的。 然而,这些项目主要使用了两个工具:Launchpad和Storyboard。

注解

Before raising a bug, story or feature request it’s important to note that not all projects do the same thing. It’s best to go check with the project to see how they handle these requests. For details on how to contact a project check the project list.

Storyboard

Storyboard 是由社区创建和维护的看板式任务跟踪系统。 它基于API-first理念设计,旨在支持跨项目工作的协调。 跟踪的项目是事件(story)和任务(task)。 事件可以是一个bug或一个新功能,而任务是完成事件所需的较小的待办事项。

For information on how to use storyboard, please see the user interface manual.

For other information about the project itself, please check out their documentation.

../_images/Storyboard.png

事件(Story)与任务(Task)

事件是一个想要的变化。 无论是bug还是新功能,两者本质上都是代码更改。 任务是事件的子项; 它们与具体项目联系在一起。 举个例子,一个事件可能是创造某个新功能A,任务将是项目X的变更,项目Y的变更,以及项目Z的变更。这些变更需要合并才能完成功能A.

看板(Board)及任务列表(Worklist)

Worklists and boards are different ways of organizing work. It is up to the project team how stories are organized. They could be sorted by milestone. A lane could have all the bugs or all the new features. It depends on the teams way of organizing and coordinating work. Order of stories in a worklist could convey priority as well.

Launchpad

Launchpad是OpenStack项目最初用于组织和定位里程碑和版本工作的任务跟踪器。 它使用UbuntuOne进行身份验证,因为它是Canonical家的。 跟踪的项目是bug或蓝图。

../_images/Launchpad.png

蓝图

在Launchpad中,一项新功能称为蓝图。 要提交新蓝图,请单击右侧的“注册蓝图”按钮。

在下一个界面上,系统会提示您添加详细信息,包括其名称和标题。

../_images/LP-overview.png

它们的不同之处在于名称是生成的URL中使用的名称,标题是列出蓝图时显示的内容(名称:new_ibm_driver 标题:New IBM ISCSI Driver)。 下一个重要的部分是摘要——对代码更改的描述,其中包含大部分有关实现的详细信息。 之后,您可能希望填写几个可选字段 - 规范(specification)网址,受让人(assignee),起草人(drafter)和审批人(approver)。 注册前的最后两个字段具有默认值 - 状态及sprint提议。 对于大多数团队而言,通常会保留默认值。

注册蓝图后,可以更新除名称和标题之外的所有信息。 当您填写完所需的所有信息后,最好与项目团队负责人沟通您已提交的蓝图。

../_images/LP-bp.png

注解

Not all projects use the blueprints feature of Launchpad, you should contact the project to see how they handle feature requests. For details on how to contact a project check the project list.

Bug

Bug非常好解释 - 软件的一些意外或无意的行为。 要报告您在Launchpad中找到的bug,请单击项目概述页面中的“报告bug”按钮。

要了解报告bug的详细信息,请填写摘要行并单击“下一步”。

../_images/LP-bug.png

Based on the summary line, Launchpad will do a quick query to see if there has been anything reported already that might be the same issue you are trying to report. It is important to look through these to avoid filing duplicate bugs and creating redundancies in the bug index. If you do not see a bug that sounds like the issue you are reporting, you can click the ‘No, I need to report a new bug’ button.

../_images/LP-bug-2.png

After clicking that button, the further information field will appear along with the ‘This bug is a security vulnerability’ radio box. You can edit the summary line to differentiate it from the other bugs Launchpad thought it was similar to, add details like the setup you were using, what you were doing when you hit the unexpected behavior, the error codes you encountered, etc.

If the bug is related to a security vulnerability it is important to click the box to alert the Vulnerability Management Team to the issue. When you feel you have added all of the information needed, go ahead and submit the bug report. For more information about the full process for reporting security vulnerabilties, please continue reading this page.

../_images/LP-bug-3.png

It is a good idea to check back on the bug routinely if you aren’t actively working on solving it to make sure people haven’t asked for more information about the issue. If someone has commented on the bug, try to respond with the details they need.

Bug Status All bugs have a status lifecycle. They start as ‘New’ and move to other statuses from there depending on what all is included in the description and if others can duplicate the issue. Resolved statuses, meaning there is no more work to be done on the bug are: ‘Fix Released’, ‘Invalid’, or ‘Won’t Fix’.

New

bug被创建

Incomplete

bug等待报告者补充

Confirmed

bug被重现或者确认为真的bug

Triaged

bug评论中出现如何正确解决此问题的完整分析

In Progress

修复工作正在进行中,bug有一个受让人

Fix Committed

暂未使用。

Fix Released

修复补丁已合并到官方分支

Invalid

不是bug

Opinion

是个有效的问题,但它应该是这样的

Won’t Fix

是个有效的问题,但我们不打算解决这个问题