Bug 190477
| Summary: | Complete initial workflow implementation and document | ||
|---|---|---|---|
| Product: | Services | Reporter: | Hiren Panchasara <hiren> |
| Component: | Bug Tracker | Assignee: | Marcus von Appen <mva> |
| Status: | Closed FIXED | ||
| Severity: | Affects Some People | CC: | bdrewery, eadler, gerald, jbeich, koobs |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
| Bug Depends on: | 190518, 190664 | ||
| Bug Blocks: | 193409 | ||
|
Description
Hiren Panchasara
2014-06-02 01:32:27 UTC
This is blocked upon bugmeister deciding to use custom templates. The concern with this is that it would preclude future updates. We would need some way to track upstream changes as well as our own patchset. We are now using (expected to use) Bugzilla for more than two months. Having https://bugs.freebsd.org/bugzilla/page.cgi?id=fields.html#bug_status not reflect those value used, day by day, in the tool, does not make sense. How can this be blocked by any (non-)action on bugmeisters side? Can you please document what you had in mind when putting in place what is in place today? And updated, if there are changes later on? *** Bug 190977 has been marked as a duplicate of this bug. *** As explained in the 'customtemplates' bug: this work is blocked on switching our deployment of bugzilla directly from the port, to the git clone we have in place. This isn't much work but has to be done carefully. My computer has been out of commission for a bit, and I'm not expecting it to return back for at least 2 weeks. If needed, I can walk someone through the necessary steps though. Marcus and I are taking care of this, and it is in progress https://bugs.freebsd.org/bugzilla/page.cgi?id=fields.html#bug_status has been updated to document the latest Bugzilla changes. Please reopen this bug, if you feel anything missing on that help page or create a new PR, if you are in the need of other, additional information. |