Re: [platform-debug-dev] Build notes policy for 3.6 development

[Curtis Windatt <Curtis_Windatt@xxxxxxxxxx>]

The bug should be assigned to the person
who fixes or is fixing the bug.  It doens't cause problems, but can
make bug searching easier.

Curtis

From:	Pawel Piech <pawel.piech@xxxxxxxxxxxxx>
To:	"Eclipse Platform Debug component developers list." <platform-debug-dev@xxxxxxxxxxx>
Date:	2009/06/22 04:41 PM
Subject:	Re: [platform-debug-dev] Build notes policy for 3.6 development

---

I have another question about process.  I see
that we're now using the 
review flag to request a review to verify a bug.  Is it OK to leave
the 
bug assigned to the inbox, or should the person fixing the bug take it
first?
Cheers,
Pawel

Darin Wright wrote:
> Developers,
>
> Historically we have maintained a detailed list of fixed bugs, new
> features and API changes/additions in 
> "/org.eclipse.debug.core/buildnotes_platform-debug.html".
Moving forward 
> for 3.6, I propose that we continue to add notes describing new features
> and API changes/additions, but not bother with a detailed list of
fixed 
> bugs. Fixed bugs are better queried from bugzilla.
>
> If you have any objections, please discuss.
>
> Darin 
> _______________________________________________
> platform-debug-dev mailing list
> platform-debug-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/platform-debug-dev
>   

_______________________________________________
platform-debug-dev mailing list
platform-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-debug-dev