On 5/29/13 3:40 PM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>> >Also, the last time we released the Installer, there was general >>confusion >> >with people thinking that we are releasing a new version of the SDK. >>We >> >should try to release new versions of the sdk and the installer as >>much as >> >possible. >> IIRC, there is some reason we can't release them together. Isn't it >>that >> the Installer can't be certified to install the latest SDK until we put >> the SDK in its final URL? I think in the past we release the SDK then >> start futzing with the Installer and several days/weeks go by. What >>would >> it take for us to feel good about releasing the Installer the same day >>or >> next day after an SDK release? >> >> >Depends on when we announce the release. Here is what I would prefer: > >1. Get flex-sdk and flex-installer both release ready >2. Generate the flex-sdk release artifacts >3. Call for a vote for flex-sdk release >4. Upload flex-sdk artifacts to dist. >5.a Wait for 24 hours for mirrors to propagate >5.b Generate flex-installer artifacts >6. Call for a vote for flex-installer release >7. Upload flex-installer artifacts to dist. >8. Wait for 24 hours for mirrors to propagate. >9. Announce flex-sdk 4.10 and flex-installer 2.6 release > >Thoughts? Seems reasonable. But isn't there some code we need to add in step 1 in order to get the installer release ready? Like getting it to somehow look at the RC's location to install from? -Alex
