Helllo; WonYoung Choi The rules is simple.
Tizen git repository should follow and follow the crosswalk upstream project. We have two branches. Master that track upstream project Tizen that add patches : - either already in review in crosswalk upstream project - or Tizen specific patches - or changes related to Tizen OBS build . This permits to avoid to wait Crosswalk upstream merge and approval and be able to release version. *All changes should be proposed in Crosswalk Upstream project.* BR Baptiste 2015-01-13 13:52 GMT+01:00 최원영 <[email protected]>: > Hello, > > > > Not long ago, the crosswalk repository ( > review.tizen.org:29418/platform/framework/web/crosswalk) was synced with > upstream (https://github.com/crosswalk-project/crosswalk) periodically. > > But some changes were merged from review.tizen.org to tizen branch > recently. > > > > Is there any changes about syncing schedule or operation policies of > crosswalk git repository? > > > > If I have some patches to apply to tizen-common or other profiles, > > Where should I submit that patches? review.tizen.org or upstream? > > > > Regards, > > WonYoung Choi > > > > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev > > -- Baptiste DURAND Eurogiciel Vannes/FR
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
