Song,
Thanks for pointing the white board info out. 684 is med enhancement, in general, people should focus on bug fixing. Enhancements will be pushed out for post 1.1 unless people has no bug to work on and has bandwidth to work on enhancement. 932 is waiting for upstream, I don't think that should impact the bug priority but may impact whether the bug can be resolved in M4. Thanks, Jessica From: Liu, Song Sent: Friday, August 05, 2011 5:31 PM To: Zhang, Jessica; [email protected] Subject: RE: M4 is bug fixing and stabilization milestone Jessica, the following 2 bugs have comments in the whiteboard asking not to include them in 1.1 or lower the priority to low. I'm not sure if you guys missed those or do not agree with the owners. Would you please double check them? 684 932 Thanks, Song From: [email protected] [mailto:[email protected]] On Behalf Of Zhang, Jessica Sent: Friday, August 05, 2011 9:18 AM To: [email protected] Subject: [yocto] M4 is bug fixing and stabilization milestone Hi All, As we marching into our final milestone M4, which is bug fixing and stabilization, the bug triage team did a bug scrub on the medium+low bugs (since we've been closely monitoring the high and major bugs) + the new multilib bugs to set a correct target for the bugs. We urge people to please start working on their bugs since bug fixing is as important as feature implementation as to ensure a successful release. Here're couple guidelines that the bug triage team want to call out: 1. Please use the whiteboard field to update your bug status between "accept" and "fixed" stage. Couple example entries like, still under development, patch out for review, etc. 2. As to general bug fixing priority order, Critical and Major bugs are must be resolved for milestone. Medium bugs should be resolved by release. And once we entered RC build phase. To ensure stability, in general we will stop accepting medium bug fixes into the release branch. Here's a link to the list of 1.1 bugs(http://bugzilla.pokylinux.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=---&target_milestone=1.1&target_milestone=1.1%20M1&target_milestone=1.1%20M2&target_milestone=1.1%20M3&target_milestone=1.1%20M4&target_milestone=Q1&target_milestone=Q2&target_milestone=Q3&target_milestone=Q4). <http://bugzilla.pokylinux.org/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ACCEPTED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=WaitForUpstream&target_milestone=---&target_milestone=1.1&target_milestone=1.1%20M1&target_milestone=1.1%20M2&target_milestone=1.1%20M3&target_milestone=1.1%20M4&target_milestone=Q1&target_milestone=Q2&target_milestone=Q3&target_milestone=Q4).%20%20> Here's a link to the 1.1 RC build schedules (https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule#M4_.28Aug_15_to_Oct_6_--_Stabilize_Complete_Aug_29.2C_Release_Complete_Oct_3.29<https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule%23M4_.28Aug_15_to_Oct_6_--_Stabilize_Complete_Aug_29.2C_Release_Complete_Oct_3.29>), so you can plan your bugs' fixes accordingly. Thanks for your hard works and continuous contributions to the Yocto Project. Jessica
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
