Re: train-41 shortened dev cycle?
I just wanna make sure we aren't sweating at the last moment, I'll go back through the items today and see whether there is anything that wouldn't work with a revised schedule. Shane On Wed, Jul 1, 2015 at 10:25 PM, Ryan Kelly rfke...@mozilla.com wrote: On 1/07/2015 13:33, Shane Tomlinson wrote: I thought initially we were going to cut at Whistler and keep the schedule as is. If the train is delayed a week, we have to make sure that doesn't cause knock on effects for the Fx 40 release with the new firstrun flow. Are there items you're specifically worried about us missing/changing for that release? Ryan On Wed, Jul 1, 2015 at 9:30 PM, John Morrison jmorri...@mozilla.com mailto:jmorri...@mozilla.com wrote: On 07/01/15 10:53, Ryan Kelly wrote: Hi All, As noted in the engineering standup on Monday, we cut train-40 a week late due to Whistler, so we're currently off our standard release cycle. Let's try to get back on schedule ASAP by doing a short dev cycle for train-41. What this would mean in practice: * Train-40 is going into production a week later than it ordinarily would have, week of Monday 6th July. * Let's cut train-41 on schedule, also week of Monday 6th July. * To ensure a smooth and simple release, let's avoid any string changes for train-41. Does this sound OK? :jrgm, how does this sound from your perspective? Sure I suppose it works. But I thought it was already settled that it wouldn't be next week. John ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org mailto:Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
Re: train-41 shortened dev cycle?
On 1/07/2015 13:30, John Morrison wrote: On 07/01/15 10:53, Ryan Kelly wrote: Hi All, As noted in the engineering standup on Monday, we cut train-40 a week late due to Whistler, so we're currently off our standard release cycle. Let's try to get back on schedule ASAP by doing a short dev cycle for train-41. What this would mean in practice: * Train-40 is going into production a week later than it ordinarily would have, week of Monday 6th July. * Let's cut train-41 on schedule, also week of Monday 6th July. * To ensure a smooth and simple release, let's avoid any string changes for train-41. Does this sound OK? :jrgm, how does this sound from your perspective? Sure I suppose it works. But I thought it was already settled that it wouldn't be next week. Just to cycle back to this on list, we decided to proceed with the above plan and cut train-41 on schedule on Monday. Ryan ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
Re: train-41 shortened dev cycle?
On 07/01/15 10:53, Ryan Kelly wrote: Hi All, As noted in the engineering standup on Monday, we cut train-40 a week late due to Whistler, so we're currently off our standard release cycle. Let's try to get back on schedule ASAP by doing a short dev cycle for train-41. What this would mean in practice: * Train-40 is going into production a week later than it ordinarily would have, week of Monday 6th July. * Let's cut train-41 on schedule, also week of Monday 6th July. * To ensure a smooth and simple release, let's avoid any string changes for train-41. Does this sound OK? :jrgm, how does this sound from your perspective? Sure I suppose it works. But I thought it was already settled that it wouldn't be next week. John ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
Re: train-41 shortened dev cycle?
On 1/07/2015 13:33, Shane Tomlinson wrote: I thought initially we were going to cut at Whistler and keep the schedule as is. If the train is delayed a week, we have to make sure that doesn't cause knock on effects for the Fx 40 release with the new firstrun flow. Are there items you're specifically worried about us missing/changing for that release? Ryan On Wed, Jul 1, 2015 at 9:30 PM, John Morrison jmorri...@mozilla.com mailto:jmorri...@mozilla.com wrote: On 07/01/15 10:53, Ryan Kelly wrote: Hi All, As noted in the engineering standup on Monday, we cut train-40 a week late due to Whistler, so we're currently off our standard release cycle. Let's try to get back on schedule ASAP by doing a short dev cycle for train-41. What this would mean in practice: * Train-40 is going into production a week later than it ordinarily would have, week of Monday 6th July. * Let's cut train-41 on schedule, also week of Monday 6th July. * To ensure a smooth and simple release, let's avoid any string changes for train-41. Does this sound OK? :jrgm, how does this sound from your perspective? Sure I suppose it works. But I thought it was already settled that it wouldn't be next week. John ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org mailto:Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
train-41 shortened dev cycle?
Hi All, As noted in the engineering standup on Monday, we cut train-40 a week late due to Whistler, so we're currently off our standard release cycle. Let's try to get back on schedule ASAP by doing a short dev cycle for train-41. What this would mean in practice: * Train-40 is going into production a week later than it ordinarily would have, week of Monday 6th July. * Let's cut train-41 on schedule, also week of Monday 6th July. * To ensure a smooth and simple release, let's avoid any string changes for train-41. Does this sound OK? :jrgm, how does this sound from your perspective? Cheers, Ryan ___ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
