README.mozilla 1.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849
  1. This is the ANGLE project, originally from https://chromium.googlesource.com/angle/angle
  2. The Mozilla upstream is the 'mozilla' branch from https://github.com/mozilla/angle, which
  3. includes Mozilla-specific patches on top of upstream.
  4. === How to upgrade ANGLE ===
  5. 1. git clone https://github.com/mozilla/angle angle
  6. 2. Go into the angle dir, and add the google upstream as a remote:
  7. git remote add google https://chromium.googlesource.com/angle/angle
  8. 3. Fetch the new google upstream:
  9. git fetch google
  10. 4. Switch to the mozilla branch
  11. git checkout mozilla
  12. 5. Rebase the mozilla branch on top of the new google master. Fix up patches along the way,
  13. remove unneded commits. Google seems to have "chromium/2059" branches as well, that I
  14. assume are merges into the Chromium tree. These might be a good point to rebase on
  15. as well, instead of google/master:
  16. git rebase -i google/master
  17. or git rebase -i google/chromium/2081 (whatever the latest is in 'git branch -a')
  18. 6. Re-generate moz.build files:
  19. ./gyp_mozbuild
  20. 7. nuke mozilla-central/gfx/angle directory
  21. 8. copy all the relevant files from the github checkout
  22. cd mozilla-central
  23. mkdir gfx/angle
  24. cp -r /c/proj/angle/[A-Z]* /c/proj/angle/{include,src,moz.build} gfx/angle
  25. 9. Build. Fix things until it builds.
  26. 10. Try runs and reviews!
  27. 11. Once reviews are done and checkin is ready, tag the equivalent git repo:
  28. git tag -a mozilla-bug-123456 -m "ANGLE update for bug 123456"
  29. 12. Push the new mozilla branch, along with the tags upstream:
  30. git push --tags mozilla +mozilla
  31. The "mozilla" branch head will keep moving, since it will keep getting rebased.
  32. The tags will point to the topmost commit that was used for a particular bug number,
  33. so that we can see its history if needed.