More about WebKit and Jellybean not being updated. This is the same line we've been saying, but a lot of users have been completely disregarding. So, I don't know where we should go from here:
https://plus.google.com/117193854832907724231/posts/1md7ruEwBLF On Fri, Jan 23, 2015, 11:34 AM Joe Bowser <bows...@gmail.com> wrote: > Marcel posted it a few days ago. I haven't seen anything come out of it > yet, but this is a big deal. > > > https://community.rapid7.com/community/metasploit/blog/2015/01/11/google-no-longer-provides-patches-for-webview-jelly-bean-and-prior > > On Fri Jan 23 2015 at 11:32:48 AM Andrew Grieve <agri...@chromium.org> > wrote: > >> Not sure what the JB fiasco is, but merging SGTM. We can always work off >> of >> 3.7.x if we end up needing another 3.x release. >> >> On Fri, Jan 23, 2015 at 1:51 PM, Joe Bowser <bows...@gmail.com> wrote: >> >> > Hey >> > >> > So, now that 3.7.0 is mostly out the door (dealing with npm stuff now), >> I >> > think we should talk about getting 4.0.x merged into master and out the >> > door. >> > >> > I know there's that CookeManager thing that breaks the File Transfer >> plugin >> > that we have to deal with, and I'm wondering if we can actually get some >> > tests for that before we do the merge. I really want 4.0.x to be in >> > mainline and be our priority so that we can get it out by the end of >> > January. >> > >> > Also, once we get 4.0.x, we need to talk about WebViews and how we deal >> > with the whole Jellybean fiasco, but I think we need to take one step >> at a >> > time and get 4.0.x out. >> > >> > Thoughts? >> > >> > Joe >> > >> >
