Bugzilla – Full Text Bug Listing
| Summary: | move Mylyn Reviews project | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Steffen Pingel <steffen.pingel> |
| Component: | Mylyn | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | alvaro.sanchez-leon, emo, kilian.matt, mario.bernhart, sharon.corbett, stefan.reiterer, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 328393 | ||
|
Description
Steffen Pingel
Webmaster, what are the option for restructuring Bugzilla components? Is it possible to rename or delete existing components (given there are no bugs assigned to the component)? It might be simplest to consolidate the existing Bugzilla components under Framework and then create new components for Gerrit, R4E, SCM and Tasks. (In reply to comment #1) > Webmaster, what are the option for restructuring Bugzilla components? Is it > possible to rename or delete existing components (given there are no bugs > assigned to the component)? We can do either of these. With any move there is some risk of data 'loss' (version or milestone) but we do our best to mitigate it. All we(webmaster) really need is a very clear map of what goes where and how to find it. Also note any 'new' generic inboxes that you may require. -M. Thanks. For the Reviews project Bugzilla migration should be straight forward then, since it does not have versions or milestones defined, yet. I would suggest the following: * Rename Bugzilla product from "Mylyn.Reviews" to "Mylyn Reviews" * Create new Bugzilla components: Framework, Gerrit, SCM, Tasks * Move all existing bugs to Framework component * Remove core, cvs, egit, subclipse, subversive, ui components Mario, can you confirm that this is in accordance with what has been discussed? I'm okay with using mylyn-inbox@eclipse.org and mylyn-triaged@eclipse.org as a general inboxes for all Mylyn sub-projects but sub-project leads may want to have their own inbox. Query for all existing Mylyn Reviews bugs: https://bugs.eclipse.org/bugs/buglist.cgi?classification=Tools;query_format=advanced;product=Mylyn.Reviews I have created mylyn.reviews in the Foundation Database. Would we need to submit a NPPR or what is the next step? The project already exists, so this is a move. No NPPR is required. You need to detail what changes need to happen and then let the webmaster/Sharon know when to start. (In reply to comment #3) > Thanks. For the Reviews project Bugzilla migration should be straight forward > then, since it does not have versions or milestones defined, yet. > > I would suggest the following: > > * Rename Bugzilla product from "Mylyn.Reviews" to "Mylyn Reviews" > * Create new Bugzilla components: Framework, Gerrit, SCM, Tasks > * Move all existing bugs to Framework component > * Remove core, cvs, egit, subclipse, subversive, ui components > > Mario, can you confirm that this is in accordance with what has been discussed? > > I'm okay with using mylyn-inbox@eclipse.org and mylyn-triaged@eclipse.org as a > general inboxes for all Mylyn sub-projects but sub-project leads may want to > have their own inbox. +1 in reply to comment #3: The list of components is missing r4e: * Create new Bugzilla components: Framework, Gerrit, SCM, Tasks is should be: * Create new Bugzilla components: Framework, Gerrit, SCM, Tasks, R4E Steffen, could you please confirm ? Thanks for pointing that out. As per discussion on the mailing list we have agreed on the following steps: * Rename Bugzilla product from "Mylyn.Reviews" to "Mylyn Reviews" * Create new Bugzilla components: Framework, Gerrit Connector, R4E, Tasks Connector * Make mylyn-inbox@eclipse.org the default assignee for all components * Move all existing bugs to Framework component * Remove Bugzilla components: core, cvs, egit, subclipse, subversive, ui Webmasters, please let me now if you need more details to go ahead with the changes. Wayne, Sharon, can we go ahead with changing the project id from tools.mylyn.reviews to mylyn.reviews to move existing CQs etc? (In reply to comment #11) > Wayne, Sharon, can we go ahead with changing the project id from > tools.mylyn.reviews to mylyn.reviews to move existing CQs etc? Sharon, the new project id has already been created. IPzilla CQs have been now been moved from tools.mylyn.reviews to mylyn.reviews. All committer paperwork has been verified and there are no barriers to moving the Committers from tools.mylyn.reviews to mylyn.reviews. Webmaster: Can you please script the necessary changes to the committer records in the DB. Thanks, Sharon IP Team We have two running elections. I hope that won't complicate the process too much. If necessary we can cancel and restart the elections. I've moved the committers and bugs so those should be all set. I updated the project fields for the running elections so those should proceed normally. If something falls over please let us know and we'll handle it manually. -M. Thanks! I think we are done here. |