The current train-2013.04.12 is on physical scl2 stage now, and slated for production deploy 2013.04.24. Which is a bit of pain in lining things up (which goes first, what if 04.12 has problems in test on stage).
But anyways, let's be optimistic, and update aws stage to be on the same train while we complete work on aws stage, so switch aws stage to use train-2013.04.12 (details on the rpm are in https://bugzilla.mozilla.org/show_bug.cgi?id=862032).
The current train-2013.04.12 is on physical scl2 stage now, and slated for production deploy 2013.04.24. Which is a bit of pain in lining things up (which goes first, what if 04.12 has problems in test on stage).
But anyways, let's be optimistic, and update aws stage to be on the same train while we complete work on aws stage, so switch aws stage to use train-2013.04.12 (details on the rpm are in https://bugzilla.mozilla.org/show_bug.cgi?id=862032).