On Tue, Jul 28, 2015 at 5:16 PM, Ryan Kelly <[email protected]> wrote:
> On 29/07/2015 07:00, Nicholas Alexander wrote: > > On Sun, Jul 26, 2015 at 5:50 PM, Ryan Kelly <[email protected] > > <mailto:[email protected]>> wrote: > > This would put us squarely in alignment with the Firefox 43.X > > development cycles, like so: > > > > * Firefox 43.1 == FxA train-44 > > * Firefox 43.2 == FxA train-45 > > * Firefox 43.3 == FxA train-46 > > * etc... > > > > At which point we might consider just adopting their naming scheme as > > well, but let's not change too many things at once :-) > > > > It would also mean that we have our train *deployments* offset by a > week > > from Firefox releases, unlike train-43 with is scheduled to go live > the > > same week as the Firefox 40 release. I think this will be a good > thing > > for overall release and quality management. > > > > > > Thoughts? > > > > > > As a client engineer who will care more and more about FxA trains and > > features, I'm a big +1 to aligning; but the fact that deployment is > > mis-aligned surprises me. I suppose what you're saying is that a web > > feature that the client depends on will always *lead* by a cycle, not > > *drag* by a cycle; i.e., that synchronized features will always be > > developed in earlier web versions that precede client versions, so that > > the deployment is always in advance of the moving client. Is that > correct? > > We will need to lead, yes. But as Sean points out, we're talking 2-week > cycles here, not full Firefox release cycles. > > Concretely, if client needs a feature at the end of the Fx43 development > cycle, we'll have to make sure that we get it done in Fx43.2 so that > it's deployed in time for the corresponding client release. > Aye. I wasn't clear: originally, my message said "week" but I changed it to cycle and didn't clarify that I mean XX.Y two-week cycle. Anyway, this works for me. Nick
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
