Hi All, I maintain a 32 rebasing cycle dashboard on https://docs.google.com/a/intel.com/spreadsheet/ccc?key=0AsFIcUvdloeddEJ1NTRPUThUaWRfUjlXR1hzbkk2NVE&usp=sharing#gid=0
The current code is based on 32.0.1700.4(I will update the latest dev version when is ready to push). So far, there are some issues is fixing: 1. Xwalk on windows crash(Shiliu/Ningxin is taking care) 2. Xwalk instrumentation test crash (Yongsheng is taking care) 3. Xwalk testing on Tizen device(Halton is taking care) Opens: 1. I created 23 more commits to fix crosswalk repo issues, each commit either fix a compiler issue or a crash issue. You could get the latest list from https://github.com/halton/crosswalk/commits/master . My question is should I merge all above commits into one? Personally, I prefer one commits fix one issue, it is more clear that why the code change like that. NOTE, I add the reversion that cause the xwalk code change. For example: commit 27000c53350ce4bc6c32d859c08211a5f323566f Author: Halton Huo [email protected]<mailto:[email protected]> Date: Tue Nov 12 11:25:42 2013 +0800 [Tizen] Add ET_GESTURE_SHOW_PRESS case to fix gcc error. Introduced by src@230206 2. What the rule of xwalk build version should be? Currently I use 3.32.4.0 (4 from 1700.4). Any suggestions or comments? BTW, I won't call for repo freeze until I'm ready for push the rebasing code. Thanks, Halton.
_______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
