On 12/7/10 10:05 AM, "Kok, Auke-jan H" <[email protected]> wrote:

> On 12/07/10 09:59, Selbak, Rolla N wrote:
>> On 12/7/10 9:57 AM, "Kok, Auke-jan H"<[email protected]>  wrote:
>> 
>>> On 12/07/10 09:50, Selbak, Rolla N wrote:
>>>> On 12/7/10 9:48 AM, "Auke Kok"<[email protected]>   wrote:
>>>> 
>>>>> On 12/07/10 03:33, Zhu, Peter J wrote:
>>>>>> Did this fix BMC#3884? If yes, mark status to Resolved/Fixed.
>>>>>> 
>>>>>> We don't accept sr with a bug that's not resolved
>>>>> 
>>>>> early calidation on my side shows that it solves one case of sreadahead
>>>>> not always finishing properly, but there are other issues with
>>>>> sreadahead that remain unsolved.
>>>>> 
>>>>> so, I can't mark the bug as resolved but this changes fixes an immediate
>>>>> issue.
>>>>> 
>>>>> partial fix?
>>>> 
>>>> Can you file a bug against the immediate issue it fixes, cite it, and set
>>>> it
>>>> to resolved?
>>> 
>>> 
>>> BMC#10987
>> 
>> Awsome, thanks.  Pleaes refer to that in your commit, and we should be all
>> good.
>> 
>> (fyi, sometime in the future, these checks will be automatic, so that's why
>> we're getting folks used to the enforced process right now)
> 
> well, this still leaves me clean in the dark about 10607 and how I'm now
> supposed to drive debugging features into components.
> 
> do I really need to file a bugzilla for each development component or
> debugging feature I intend to add to core components? that's a huge
> waste of my time in pure "paperwork"...

Yes, that was the process that was decided.

I agree it takes more paperwork than folks would like (even on our Release
Engineering side), but it's much easier and efficient to track code coming
in and their purpose (and there's a lot of code coming in, and it's not even
cut-off time yet)

Breaking up features or bugs into subs is a good way of doing things if you
can't fulfill a bug or feature completely...

Also of course bugs and features get reopened if QA finds the bug or feature
isn't fix as well...


rs

> 
> Auke
> 

_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to