PageRenderTime 24ms CodeModel.GetById 8ms RepoModel.GetById 1ms app.codeStats 0ms

/betterrev/src/main/angularjsapp/app/partials/help.html

https://bitbucket.org/arkangelofkaos/betterrev
HTML | 102 lines | 92 code | 9 blank | 1 comment | 0 complexity | f6114566d76bf4bac60dc96b29742468 MD5 | raw file
  1. <h2 id="helpHeading">I need help from a real Human!</h2>
  2. <p>
  3. <a href="#contactus"><img src="images/Icon_Arrow_60x60px.png" alt="Contact Us"/> Contact Details</a>
  4. </p>
  5. <h2>How do I start?</h2>
  6. <p>
  7. If you're new to Betterrev then you'll want to do the following:
  8. </p>
  9. <ol>
  10. <li>Create a <a href="https://bitbucket.org/" target="_blank">BitBucket</a> account</li>
  11. <li>Join the <a href="https://bitbucket.org/adoptopenjdk/" target="_blank">Adopt OpenJDK BitBucket Organisation</a>
  12. </li>
  13. <li>Fork all the JDK repositories
  14. <ul>
  15. <!-- TODO -->
  16. <li><a href="https://bitbucket.org/adoptopenjdk/jdk9" target="_blank">jdk9</a></li>
  17. </ul>
  18. </li>
  19. <li>Clone the adopt repo and really get started!<br />
  20. <br />
  21. <pre>
  22. hg clone ssh://hg@@bitbucket.org/adoptopenjdk/adopt
  23. cd adopt
  24. ./start.sh your-bitbucket-username
  25. </pre>
  26. <br />
  27. You should see something that looks like:<br />
  28. <br />
  29. <p class="console-output">
  30. richardwarburton@@machine:openjdk$ hg clone ssh://hg@@bitbucket.org/adoptopenjdk/adopt <br/>
  31. destination directory: adopt <br/>
  32. requesting all changes <br/>
  33. <br/>
  34. ...<br/>
  35. <br/>
  36. jdk: 21818 files updated, 0 files merged, 0 files removed, 0 files unresolved <br/>
  37. marked working directory as branch richardwarburton <br/>
  38. </p>
  39. <p>
  40. The above commands should have created a branch (branch name is same your Bitbucket username). <br/>
  41. If you wish to create your own branch, please use the command hg branch YOURBRANCHNAME.
  42. </p>
  43. </li>
  44. </ol>
  45. <h2>What is Betterrev all about?</h2>
  46. <p>
  47. Betterrev is a website and workflow to help improve the velocity and quality
  48. of patches going into <a href="http://openjdk.java.net" target="_blank">OpenJDK</a>.
  49. It does this by:
  50. </p>
  51. <ol>
  52. <li>
  53. Providing up to date clones of OpenJDK forests in <a href="https://bitbucket.org/" target="_blank">BitBucket</a>
  54. </li>
  55. <li>Allowing a Pull Request model for submitting patches</li>
  56. <li>Providing a trackable workflow for a submitted patch (via this website)</li>
  57. <li>Automatically generating a Webrev for a given patch</li>
  58. <li>Automatically building the patch and running jtreg tests on major platforms (Continuous Integration)</li>
  59. <li>Automated requests for sponsors in the correct OpenJDK mailing lists for a patch</li>
  60. </ol>
  61. <h2>What's the behind the scenes workflow?</h2>
  62. <p>We simplify things as much as possible for the end user, but for those who are curious</p>
  63. <p>
  64. A typical workflow works as follows (you will be notified at each stage):
  65. </p>
  66. <ol>
  67. <li><strong>Betterrev</strong> keeps up to date copies of OpenJDK repos in BitBucket</li>
  68. <li><strong>You</strong> fork the appropriate <a href="https://bitbucket.org/adoptopenjdk/" target="_blank">OpenJDK repo(s)</a> from BitBucket
  69. </li>
  70. <li><strong>You</strong> submit a Pull Request for your patch via BitBucket</li>
  71. <li><strong>Betterrev</strong> will create what's known as a Contribution</li>
  72. <li><strong>Betterrev</strong> will build your Contribution on a Build Farm (TODO)</li>
  73. <li><strong>Betterrev</strong> will run the JTReg regression test suite over your Contribution (TODO)</li>
  74. <li><strong>Betterrev</strong> will generate a Webrev for you</li>
  75. <li><strong>Betterrev</strong> will discover which mailing lists you need to send the Webrev to</li>
  76. <li><strong>You</strong> can then send a message (through the BetterRev site) to the mailing lists.</li>
  77. <li>
  78. <strong>You</strong> will need to follow up on comments from those mailing lists and update your
  79. BitBucket Pull Request accordingly.
  80. </li>
  81. <li><strong>Betterrev</strong> will automatically update the Contribution based on your changes and the cycle begins again</li>
  82. <li>When your Webrev is accepted, it will be committed through the normal OpenJDK channels</li>
  83. <li><strong>Betterrev</strong> will archive your Contribution (and BitBucket Pull Request)</li>
  84. </ol>
  85. <h2>Why is it called Betterrev?</h2>
  86. <p>
  87. The official way to submit a patch to OpenJDK is through a tool called Webrev.
  88. Webrev is a barrier for some contributors as it is only supported on some
  89. operating systems and requires you to host a static web site for your patch.
  90. </p>
  91. <p>
  92. So we decided to create a workflow called Betterrev to remove this barrier!
  93. </p>