Community
Participate
Working Groups
Right now, I know we need to update the Eclipse 3.7.1 and 4.1.1 builds to the appropriate bases: M20110909-1335 for Eclipse 3.7.1 M20110912-1510 for Eclipse 4.1.1 As other components that we rely on update their base components, I will need to update those as well.
For Dali we need to update EclipseLink to the build released for SR1 EclipseLink 2.3.1.v20110908-r10021 M5
As far as I can tell, those were the only prereqs that have updated in the last week. It would appear that we are good to go for Indigo SR1 once we recompile on these updated prereqs. I am submitting this for PMC approval as a courtesy, and to follow the outlined process. These changes will be delivered immediately, and a build will happen in preparation for our SR1 contribution. Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. This is stop-ship because we need to ensure that we compile against (and test against) the final Indigo SR1 prereqs Is there a work-around? If so, why do you believe the work-around is insufficient? There is no workaround How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? The "fix" has not been tested. However, it will be smoke tested as part of our final shutdown for Indigo SR1 Give a brief technical overview. Who has reviewed this fix? We are moving up to the Indigo SR1 prereqs. Nobody has reviewed this "fix". What is the risk associated with this fix? This is a medium risk fix- there is a chance that a base prereq change could break us. However, it is a necessary risk.
approved thanks carl
These updates were made.
