-
Enhancement
-
Resolution: Fixed
-
P2
-
6u25
-
b01
-
x86
-
windows
-
Verified
AU version 2.0.4.1 contains 2 CRs that have been requested for 6u25:
7001270: Auto Update Schedule should have a flexible weekly update check for critical releases
* This CR was requested by Jeannette to be backported to 6u25
7008448: PC-OEM would like a way to disable prompt to user with new laptop that new JRE version is availab
* This CR is a external request from a PC-OEM that was also approved by Jeannette for 6u25
In addition to those 2 fixes, there are 2 additonal CRs required to fix defects found in original implementation of the Flexible AU feature:
7006311: PIT: Cannot Auto update with flexible schedule - spawning multiple javaws/javaw/jaucheck processes
7009355: Scheduler incorrectly picks critical schedule in some cases
CRs 7001270 & 7006311 (Flex AU and one of the flex AU fixes) have already been through a full PIT and promotion test cycle with no regressions. They were directly pulled into the 2.0.X repository so there is very little risk associated with them. The remaining 2 fixes are new, but are relatively minor fixes for optional features and should have very low risk to core behavior.
7001270: Auto Update Schedule should have a flexible weekly update check for critical releases
* This CR was requested by Jeannette to be backported to 6u25
7008448: PC-OEM would like a way to disable prompt to user with new laptop that new JRE version is availab
* This CR is a external request from a PC-OEM that was also approved by Jeannette for 6u25
In addition to those 2 fixes, there are 2 additonal CRs required to fix defects found in original implementation of the Flexible AU feature:
7006311: PIT: Cannot Auto update with flexible schedule - spawning multiple javaws/javaw/jaucheck processes
7009355: Scheduler incorrectly picks critical schedule in some cases
CRs 7001270 & 7006311 (Flex AU and one of the flex AU fixes) have already been through a full PIT and promotion test cycle with no regressions. They were directly pulled into the 2.0.X repository so there is very little risk associated with them. The remaining 2 fixes are new, but are relatively minor fixes for optional features and should have very low risk to core behavior.