[wtp-dev] Bug fix handling during our shutdown

[David M Williams <david_williams@xxxxxxxxxx>]

I have updated our "1.5 plan and
policies" document to include a paragraph on bug/fix handling during
the shutdown. 
I'm sure more ~could~ be said on this
topic, but the important part for now is to make sure we make it easy for
testers and 
adopters to verify (or use!) the fixes
for any blocking defects they've found and we fix. This allows for quick
preliminary 
verification of these critically important
bugs. 

I've written a paragraph in 
http://wiki.eclipse.org/index.php/WTP_Release_1.5.x_Maintenance_Plan_and_Policies#End_Game_Bug_Triage
as below. 

Please let me know if questions, or
if you see places where it could easily be improved. 
We can discuss at today's status call,
if there are issues concerning this. 

Thanks

= = = = = 

End Game Bug Triage

Especially during the final month/weeks of a release, when we are mostly fixing serious regressions and blocking defects, it is important to let the originator know how to "get the fix" to verify, or unblock their testing. In some cases, it might be easiest/best to attach a "development built" jar to the bugzilla (just make sure the qualifier in the plugin version is appropriate ... usually something like v{date-time}_devfix would work).

But, at a minimum, be sure to leave a note in the bug which "continuous build" you expect the fix to be in, and which plugin or plugins would contain the fixes, if possible. A URL to that build is ideal, but if you have to, you can "guess" and say something like "In continuous builds greater than Mxxxx", where xxxx is current date and time plus about 4 hours from the time you release it. And, then, ideally, you can verify which build contained the fix and update the bugzilla entry with more precision.