Hi Raphael, I found current Chromium version in crosswalk 'next' branch is 34.0.1809.2. However, according to OmahaProxy [1] and Chromium developer calendar [2], the current Chromium dev is 34.0.1838.2 and the 34 branch point is 17th Feb. So I concern that the 34.0.1809.2 will not be promoted to beta in upstream. It means we might need another rebase (maybe 34.0.1838.3) before we switch the master to M34.
Is that the case? If I misunderstand the rebase process, please feel free to correct me. Thanks, -ningxin [1]: http://omahaproxy.appspot.com/ [2]: http://www.chromium.org/developers/calendar > -----Original Message----- > From: Crosswalk-dev > [mailto:[email protected]] On Behalf Of > Raphael Kubo da Costa > Sent: Tuesday, February 18, 2014 11:46 PM > To: [email protected] > Subject: [Crosswalk-dev] M34 rebase status > > Fellow pedestrians, > > I would like to switch crosswalk-master to M34 tomorrow (2014-02-19), which > means the tree would be closed for new merges until we switch and the bots > get green. This will probably happen after PRC work hours so you guys don't > necessarily have to stop merging pull requests altogether, but please use your > best judgment to only merge things tomorrow if absolutely required, otherwise > I will have to rebase next on top of the new master and things might break. > > I have rebased the next branch on top of the current master (322bc6d) and > added a few commits at the top bumping chromium-crosswalk and > ozone-wayland revisions and also making some changes to the Tizen spec file > required for building and running Crosswalk. In total, we currently have 32 > commits in the next branch that will be squashed into a single one so that we > don't end up with a broken tree between master and the 31 commits preceding > the last one. > > Some new commits were merged into chromium-crosswalk's master branch > today; I have asked in the respective pull requests whether they are needed in > chromium-crosswalk's next branch too. They are also in the spreadsheet [1]. My > idea is to move on without them even if they are required in next to avoid > delaying things even further; they can just be reintegrated later again. > > [1] > https://docs.google.com/a/intel.com/spreadsheet/ccc?key=0ApeGmzZEJ05GdF > BOWHBtSmM1UzE1bDlUUkRJdWgyX0E > > Since it's been around 20 days since Alexis branched next off master and > started > working on M34, I am not entirely sure all platforms are still working after I > rebased next on top of the current master: I've only tested Linux, Tizen 3 > Mobile > and Tizen IVI. I was hoping to rely on the trybots for the rest, but if you > guys can > verify Windows, Android and Mac and send pull requests if needed, I'd > appreciate it. > > Happy hacking. > _______________________________________________ > Crosswalk-dev mailing list > [email protected] > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
