(remix; see http://lists.meego.com/pipermail/meego-qa/2011-June/001953.html for more info) |
(→How MeeGo Bugzilla requests are handled) |
||
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
=Processes to handle MeeGo Bugzilla Requests= | =Processes to handle MeeGo Bugzilla Requests= | ||
| - | DRAFT STATUS - see [http://lists.meego.com/pipermail/meego-qa/2011-June/001940.html | + | DRAFT STATUS - see [http://lists.meego.com/pipermail/meego-qa/2011-June/001940.html 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. | 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== | ==How MeeGo Bugzilla requests are handled== | ||
| - | * Have a [https://bugs.meego.com/enter_bug.cgi?product=bugs.meego.com | + | * 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; |
* Error management team will provide feedback in one working day normally once receive the request notification; | * 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; | * 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 | + | * 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== | ==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 [http://gitorious.net/meego-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; | * Submit the new feature & bug fix into personal repository branch; | ||
* Merge the changes into staging branch after code cross review; | * Merge the changes into staging branch after code cross review; | ||
* Deploy the changes into staging Bugzilla; | * Deploy the changes into staging Bugzilla; | ||
| - | * Feedbacks from testing on our staging instances ([https://01.bugs-dev.meego.com/ | + | * 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; | * Merge the changes from staging branch to production branch once code quality is good enough; | ||
* Deploy the changes into production Bugzilla; | * Deploy the changes into production Bugzilla; | ||
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.