Bugzilla – Full Text Bug Listing
| Summary: | standardize on bug tags and improve components | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Steffen Pingel <steffen.pingel> |
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | robert.elves |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 304957 | ||
|
Description
Steffen Pingel
Should also decide if tags like [patch] should be removed after patch is applied. Yes, that is the current convention as documented on the Wiki page. Should we Steffen: I'll assign this to you since you're driving these good changes. The next step I suggest is to list our our Bugzilla components and remove redundancy between tags and components. Also, I figure that components should be things that end users understand (e.g. Task Editor, Task List) and the tags used more for internal stuff. It might be hard to implement all these changes now but let's at least figure out what a better structure would be. I have added the list of Bugzilla components to the Wiki page. Having a short list of components that are user recognizable could help with triageing bugs. I hardly ever use those for organizing tasks but it is useful for assigning tasks to the default component owner. Maybe that could be a criterium for defining components, e.g.: Bugzilla - Rob Doc and Website - mylyn-inbox Task List and Editor - mylyn-tasks-inbox Contexts/Task-Focused UI - mylyn-context-inbox Jira, Trac - Steffen Web - Eugene XPlanner - Helen Other - mylyn-inbox Platform seems to have an inbox per components as well. "Web" isn't going to work like this for the web connector. I believe the current one it is actually mean we web site, and we also have mylyn.web.core and mylyn.web.ui plugins that aren't mine. BTW, before creating separate component for web connector it would be really, really nice, if someone finally decide on connector name. See bug 205343 Yes, "Web" might be too generic. As Mik pointed out the components could be something recognized by users and would not have to map directly to plug-ins. Maybe a Sanbox (Incubation) component would be useful as well. Good progress, let's discuss on an upcoming call. I've linked this task in with the pending discussions. I have updated the list at http://wiki.eclipse.org/Mylyn/Contributor_Reference#Bugzilla and added it to next week's meeting agenda. Rob mentioned that he would like to add an OSLC component. Mik, I'll reassign this to you since it's related to the project restructuring. Sounds good. Let's wait until that's done, then pick this up again. Proposed structure as per message to mylyn-dev: http://dev.eclipse.org/mhonarc/lists/mylyn-dev/msg01034.html . Mylyn * Inbox, Releng, Website Mylyn Builds * B3, Framework, Hudson Mylyn Commons * Identity, Monitor, Repositories, Notifications, UI Mylyn Context * Java, C/C++, Framework, PDE, Resources Mylyn Docs * WikiText, HtmlText Mylyn Incubator * Usage Monitor, UI Experiments, Web Templates, WikiText Sandbox Mylyn Reviews * Framework, Gerrit, R4E, SCM, Tasks Mylyn Tasks * Bugzilla, Framework, OSLC, Trac Mylyn Versions * CVS, Framework, EGit, OSLC To clarify, the EGit component under Mylyn Versions is the EGit Connector for the Mylyn versions API. The JGit/EGit projects would keep their own Bugzilla products. Looks good! Nits: * "Inbox" -> "General" * Incubator: "Experiments", "Monitor", ... Thanks. The Bugzilla products and components have been provisioned. Looks like we are done here. |