| Summary: | redundant Gentoo Linux component: Keywording & stabilization | ||
|---|---|---|---|
| Product: | Gentoo Infrastructure | Reporter: | SpanKY <vapier> |
| Component: | Bugzilla | Assignee: | Bugzilla Admins <bugzilla> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | andreis.vinogradovs, pacho |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 213514 | ||
| Bug Blocks: | |||
|
Description
SpanKY
2011-09-02 21:27:33 UTC
See bug 213514 - So we probably should remove the keywords instead. I think a extra component for keywording and stabilization makes more sense than using Keywords. i dont. we have dedicated products/components for some of our packages, and injecting a new component in there doesn't work. however, Keywords is a parallel field and automatically works every existing product/component. so in the case of using Keywords, not only can the arch teams easily set up a query to locate all of the open bugs, but so can maintainers. but by breaking the Component field, maintainers can no longer easily locate all their bugs. further, having a single component makes it impossible to sort between stable requests and keyword requests. I also doubt about this, if I don't misremember, most arch teams are looking for STABLEREQ/KEYWORDREQ keywords instead of components. I am not sure about the disadvantages of using keywords as we are doing now :/ Another advantage is that we can split keywording and stabilization with the keywords Any news about this? :/ Arch teams are actively using and requiring the component, so I don't see a problem. If you want things to change, get a wider agreement. You know the drill. It looks like after the components reorganization... this was fixed ;) |
