> -----Original Message----- > From: Crosswalk-dev > [mailto:[email protected]] On Behalf Of > Raphael Kubo da Costa > Sent: Wednesday, February 19, 2014 5:27 PM > To: [email protected] > Subject: Re: [Crosswalk-dev] M34 rebase status > > "Hu, Ningxin" <[email protected]> writes: > > > 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. > > Hi, > > That's right, we will likely rebase onto a newer M34 release sometime later. > This > should not be a problem, though. Changing minor versions in the same > milestone is normally very easy and does not require freezing the tree or > adjusting the code anyway, so Alexis and I will just do it later.
Good to know that. Thanks for the explanation. I am asking this since I am working on rebasing SIMD.js v8 implementation to prepare for landing on Crosswalk-5. I've done the rebasing on v8 3.24.24 (Chromium 34.0.1809.2). However, I find when moving to v8 3.24.37 (Chromium 34.0.1838.2), there are another 13 files conflicts. So for my case, it might be better to rebase directly to v8 3.24.37 if it is the upstream beta candidate. Thanks, -ningxin > _______________________________________________ > 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
