| Summary: | add IN PROGRESS DOCUMENTATION | ||
|---|---|---|---|
| Product: | [Infrastructure] Bugzilla | Reporter: | Alexander Kanavin <alex.kanavin> |
| Component: | bugzilla | Assignee: | Michael Halstead <mhalstead> |
| Status: | IN PROGRESS DOCUMENTATION --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium+ | CC: | antonin.godard, infras.bug.watcher, Infras.watcher, randy.macleod, srifenbark |
| Version: | unspecified | ||
| Target Milestone: | Q2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
|
Description
Alexander Kanavin
2018-02-27 14:24:44 UTC
I've looked over the scripts and this should only take a few hours to add but first we need to decide if this status counts as OPEN or CLOSED for the purpose of the graphs at https://wiki.yoctoproject.org/charts/combo.html. I could make a case for either option. Bugzilla doesn't support the workflow suggested as nice as it would be. We can force all bugs to move through IN PROGRESS DOCUMENTATION or not it can't be determined based on a custom field. Just my opinion but I would say the bug is still OPEN as it should not be RESOLVED or CLOSED until all aspects are dealt with, including the documentation part. Scott Scott, I'm trying to clean up my bugzilla queue and I'm not sure what to do with this bug. We cannot make IN PROGRESS DOCUMENTATION a required part of the workflow but we can add the status to be used optionally. Would you like to add the status or leave the configuration as it is? Michael, I guess it is really a matter of educating the community on ways to work a bug through its phases given the available workflow. The fact is that most developers will mark a bug off as RESOLVED/FIXED once the code is done. Most don't think beyond that to the implications of user docs. We do have the flag that people do use. I guess we could suggest people use a new IN PROGRESS DOCUMENTATION status if it were available. Thanks, Scott I believe the question has been answered. It looks like he wants this as an optional item. Great - make it optional. Please add it Michael. Thanks, Scott Antonin, Do you think this process change would help you and/or the project? I've re-enabled IN PROGRESS DOCUMENTATION. Please let me know if it is helpful or if I should disable it again. Hi, Yes, I actually think this will be helpful both for users to be reminded of documenting their additions, and from a triage point of view. Thanks! Michael, We don't see that state in the list... Can you double check that it's actually there and working. We plan to add some documentation to guide users about the new state. I've enabled this status in all workflows. It's ready to use. |