Cool - If we are getting new features, I agree we'll be pulling in components early and regularly (a la GeckoView).
On Tue, Oct 2, 2018 at 4:05 PM Stefan Arentz <[email protected]> wrote: > > > On Tue, Oct 2, 2018 at 5:23 PM Susheel Daswani <[email protected]> > wrote: > >> My initial reaction to '[a]lways develop against components -SNAPSHOT so >> that you stay up to date' is we likely won't upgrade components versions >> unless there is product value and some assurances of stability when doing so >> > > I think this is totally fair. It is a recommendation, not a requirement. > Individual teams are totally within their right to choose how they deal > with libraries that they have pulled in. > > However, I am working on the assumption that the Android Components are > largely driven by requirements from the product teams. A lot of the work > that we have been doing the past months was the direct result of requests > for changes, new features, API improvements or even new components. > > It is a reality that our products are moving fast. And I fully expect the > product teams to put in requests for changes for pretty much every major > release of those applications. > > You get those changes early in your product development cycle by following > our snapshot builds. And you ship them by updating to a (pinned) new > release. > > I'm sure there will be exceptions, but I think we should set ourselves up > for that scenario. > > S. > > -- Susheel Daswani Senior Mobile Engineering Manager phone / text: (415) 218-7259
_______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
