Meego Wiki
Views

Quality/MeeGoBugzillaRequestProcess

From MeeGo wiki
< Quality(Difference between revisions)
Jump to: navigation, search
(→How MeeGo Bugzilla requests are handled)
 
(4 intermediate revisions not shown)
Line 1: Line 1:
-
'''Processes to handle the MeeGo Bugzilla Requests'''
+
=Processes to handle MeeGo Bugzilla Requests=
-
This process is to ensure the MeeGo Bugzilla new features or changes are implemented & deployed under the planned way and also ensure the MeeGo Bugzilla features & changes are generic enough for most of users.  
+
DRAFT STATUS - see [http://lists.meego.com/pipermail/meego-qa/2011-June/001940.html mailing list thread]
-
*Here is the brief process summary of how MeeGo Bugzilla request is handled:
+
This process is to ensure new features or changes to MeeGo Bugzilla itself are implemented & deployed under the planned way and also to ensure the MeeGo Bugzilla features & changes are generic enough for most users.
-
** Have a bug entry or feature entry for all change requests both for code level and new custom fields & new flags;
+
-
** Error management team will provide feedbacks in one working day normally once receive the request notification;
+
-
** The follow up and feedbacks could be happened at bug/feature comments;
+
-
** Use Severity field to identify how urgent & important the request is;
+
-
** The bug or feature assignee will use priority field to identify how urgent and important the request is;
+
-
** Use target milestone to indentify when the change could be ready especially for large changes need the code level customization;
+
-
** For minor change like component adjustment and component owner changes, MeeGo Bugzilla admins will go ahead directly but nice to have a bug entry for change request;
+
-
*To ensure the quality of changes bring to MeeGo bugzilla, here is the process to accept & review & integrate code level changes
+
==How MeeGo Bugzilla requests are handled==
-
** There will be a personal repository branch for each one has the source code submission privilege in MeeGo Bugzilla git repository;
+
* Have a [https://bugs.meego.com/enter_bug.cgi?product=bugs.meego.com bug report] or [https://bugs.meego.com/enter_bug.cgi?product=bugs.meego.com%20Features feature request] for the complete requests both for code level and new custom fields & new flags;
-
** Submit the new feature & bug fix into personal repository branch;
+
* Error management team will provide feedback in one working day normally once receive the request notification;
-
** Merge the changes into staging branch after code cross review;
+
* The follow up and feedbacks should happen in the bug/feature comments in the report;
-
** Deploy the changes into staging Bugzilla;
+
* For minor change like component adjustment and component owner changes, MeeGo Bugzilla admins will go ahead directly but nice to have a ticket.
-
** Feedbacks from testing on our staging instances;
+
 
-
** Merge the changes from staging branch to production branch once code quality is good enough;
+
==Process to accept & review & integrate code level changes==
-
** Deploy the changes into production Bugzilla;
+
* There will be a personal repository branch for each one has the source code submission privilege in [http://gitorious.net/meego-bugzilla MeeGo Bugzilla git repository];
 +
* Submit the new feature & bug fix into personal repository branch;
 +
* Merge the changes into staging branch after code cross review;
 +
* Deploy the changes into staging Bugzilla;
 +
* Feedbacks from testing on our staging instances ([https://01.bugs-dev.meego.com/ 1], [https://02.bugs-dev.meego.com/ 2]);
 +
* Merge the changes from staging branch to production branch once code quality is good enough;
 +
* Deploy the changes into production Bugzilla;

Latest revision as of 13:18, 17 June 2011

Processes to handle MeeGo Bugzilla Requests

DRAFT STATUS - see mailing list thread

This process is to ensure new features or changes to MeeGo Bugzilla itself are implemented & deployed under the planned way and also to ensure the MeeGo Bugzilla features & changes are generic enough for most users.

How MeeGo Bugzilla requests are handled

  • Have a bug report or feature request for the complete requests both for code level and new custom fields & new flags;
  • Error management team will provide feedback in one working day normally once receive the request notification;
  • The follow up and feedbacks should happen in the bug/feature comments in the report;
  • For minor change like component adjustment and component owner changes, MeeGo Bugzilla admins will go ahead directly but nice to have a ticket.

Process to accept & review & integrate code level changes

  • There will be a personal repository branch for each one has the source code submission privilege in MeeGo Bugzilla git repository;
  • Submit the new feature & bug fix into personal repository branch;
  • Merge the changes into staging branch after code cross review;
  • Deploy the changes into staging Bugzilla;
  • Feedbacks from testing on our staging instances (1, 2);
  • Merge the changes from staging branch to production branch once code quality is good enough;
  • Deploy the changes into production Bugzilla;
Retrieved from "http://wiki.meego.com/Quality/MeeGoBugzillaRequestProcess"
Personal tools