Summary: | Default update policy is always USER-EXCLUDE | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | James D. Miles <jdmiles> | ||||
Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Branko Tripkovic <btripkov> | ||||
Status: | RESOLVED FIXED | QA Contact: | |||||
Severity: | major | ||||||
Priority: | P1 | CC: | doug_macdonald, jeffmcaffer, pam_tobias, steven.wasleski, wassim.melhem | ||||
Version: | 3.2 | ||||||
Target Milestone: | 3.2 RC3 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
James D. Miles
2006-03-13 20:54:57 EST
Created attachment 36191 [details]
Patch to fix default policy when using MANAGED-ONLY
What is the outlook for getting this bug fixed in 3.2? We are trying to minimise the number of defects we fix for RC3. What makes this defect a must-fix for 3.2? RC3 candidate. Released. Need formal votes. Dejan adds +1. Jeff, need additional +1 before releasing. Wassim, you can help Jeff to unblock this backlog. This bug is checked and ready to go. +1 for RC3 fixed |