At the PMC call today we discussed how to advertise to adoptors which builds contain the fixes to their bugs. It would also be a good idea to do this for any fix that goes into 1.0.1.

We are trying to automate this by looking at CVS comments, however is is hard to get accurate results. Since the number of Hot Bugs is fairly low, we think it's simplest to use a manual process.

Could developers please add a comment to Bugzilla saying which M build contains the fix. So far, we have 8 fixes for Hot Bugs:


117145 cri P2 [EMAIL PROTECTED] RESO FIXE 1.0.1 M101 Cannot change context root of a WebApp using the GUI
118903 maj P2 [EMAIL PROTECTED] RESO FIXE 1.0.1 M101 Need way to have adopter-defined facets automatically app...
119051 maj P2 [EMAIL PROTECTED] RESO FIXE 1.0.1 M101 common archive NPE when the ear has Alt DD
119742 maj P2 [EMAIL PROTECTED] RESO FIXE 1.0.1 M101 runtime target not set on client jar project when ear is ...
119758 maj P2 [EMAIL PROTECTED] RESO FIXE 1.0.1 M101 No API to get context-root of static web project
120657 maj P2 [EMAIL PROTECTED] RESO FIXE 1.0.1 M101 WebArtifact edit not returning web.xml
121692 blo P2 [EMAIL PROTECTED] RESO FIXE 1.0.1 M101 Resource change takes ~1 min
122974 cri P2 [EMAIL PROTECTED] RESO FIXE 1.0.1 M101 ProjectModule on a web utility module does not return the...



Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
_______________________________________________
wtp-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/wtp-dev

Reply via email to