|
I figured it was the underlying switch to node.jsjsjs $or$ $whatever$ $the$ $new$ $framework$ $is$ $for$ $services$, $but$ $since$ $I$ $only$ $had$ $this$ $issue$ $with$ $google$ $talk$, $that$ $is$ $what$ $I$ $pegged$ $it$ $on$. $This$ $is$ $now$ $open$ $sourced$ $to$ $my$ $understanding$. $Anyway$, $I$ $don$'$t$ $know$ $how$ $the$ $bug$ $fixing$ $process$ $or$ $entire$ $version$ $release$ $process$ $will$ $work$ $once$ $webos$ $is$ $fully$ $open$ $sourced$, $but$ $here$'$s$ $hoping$ $there$ $will$ $be$ $an$ $easy$ $way$ $to$ $post$ $bug$ $reports$ $and$ $view$ $the$ $bug$ $fixing$ $process$, $like$ $any$ $good$ $open$ $source$ $product$.
Here's hoping that releases will be coming in monthly or so once its open sourced, with webos doctors (or even OTA updates, although i don't know how HP/carriers will manage this) being released at a nice clip. Although this is definitely an ideal, perfect world scenario.
Once this bug is fixed, I'm probably moving back to webos full time.
|
|
|