git.html 28 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325
  1. <!DOCTYPE HTML>
  2. <html lang="en" class="sidebar-visible no-js light">
  3. <head>
  4. <!-- Book generated using mdBook -->
  5. <meta charset="UTF-8">
  6. <title>Git Usage - Synapse</title>
  7. <!-- Custom HTML head -->
  8. <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  9. <meta name="description" content="">
  10. <meta name="viewport" content="width=device-width, initial-scale=1">
  11. <meta name="theme-color" content="#ffffff" />
  12. <link rel="icon" href="../favicon.svg">
  13. <link rel="shortcut icon" href="../favicon.png">
  14. <link rel="stylesheet" href="../css/variables.css">
  15. <link rel="stylesheet" href="../css/general.css">
  16. <link rel="stylesheet" href="../css/chrome.css">
  17. <link rel="stylesheet" href="../css/print.css" media="print">
  18. <!-- Fonts -->
  19. <link rel="stylesheet" href="../FontAwesome/css/font-awesome.css">
  20. <link rel="stylesheet" href="../fonts/fonts.css">
  21. <!-- Highlight.js Stylesheets -->
  22. <link rel="stylesheet" href="../highlight.css">
  23. <link rel="stylesheet" href="../tomorrow-night.css">
  24. <link rel="stylesheet" href="../ayu-highlight.css">
  25. <!-- Custom theme stylesheets -->
  26. <link rel="stylesheet" href="../docs/website_files/table-of-contents.css">
  27. <link rel="stylesheet" href="../docs/website_files/remove-nav-buttons.css">
  28. <link rel="stylesheet" href="../docs/website_files/indent-section-headers.css">
  29. <link rel="stylesheet" href="../docs/website_files/version-picker.css">
  30. </head>
  31. <body>
  32. <!-- Provide site root to javascript -->
  33. <script type="text/javascript">
  34. var path_to_root = "../";
  35. var default_theme = window.matchMedia("(prefers-color-scheme: dark)").matches ? "navy" : "light";
  36. </script>
  37. <!-- Work around some values being stored in localStorage wrapped in quotes -->
  38. <script type="text/javascript">
  39. try {
  40. var theme = localStorage.getItem('mdbook-theme');
  41. var sidebar = localStorage.getItem('mdbook-sidebar');
  42. if (theme.startsWith('"') && theme.endsWith('"')) {
  43. localStorage.setItem('mdbook-theme', theme.slice(1, theme.length - 1));
  44. }
  45. if (sidebar.startsWith('"') && sidebar.endsWith('"')) {
  46. localStorage.setItem('mdbook-sidebar', sidebar.slice(1, sidebar.length - 1));
  47. }
  48. } catch (e) { }
  49. </script>
  50. <!-- Set the theme before any content is loaded, prevents flash -->
  51. <script type="text/javascript">
  52. var theme;
  53. try { theme = localStorage.getItem('mdbook-theme'); } catch(e) { }
  54. if (theme === null || theme === undefined) { theme = default_theme; }
  55. var html = document.querySelector('html');
  56. html.classList.remove('no-js')
  57. html.classList.remove('light')
  58. html.classList.add(theme);
  59. html.classList.add('js');
  60. </script>
  61. <!-- Hide / unhide sidebar before it is displayed -->
  62. <script type="text/javascript">
  63. var html = document.querySelector('html');
  64. var sidebar = 'hidden';
  65. if (document.body.clientWidth >= 1080) {
  66. try { sidebar = localStorage.getItem('mdbook-sidebar'); } catch(e) { }
  67. sidebar = sidebar || 'visible';
  68. }
  69. html.classList.remove('sidebar-visible');
  70. html.classList.add("sidebar-" + sidebar);
  71. </script>
  72. <nav id="sidebar" class="sidebar" aria-label="Table of contents">
  73. <div class="sidebar-scrollbox">
  74. <ol class="chapter"><li class="chapter-item expanded affix "><li class="part-title">Introduction</li><li class="chapter-item expanded "><a href="../welcome_and_overview.html">Welcome and Overview</a></li><li class="chapter-item expanded affix "><li class="part-title">Setup</li><li class="chapter-item expanded "><a href="../setup/installation.html">Installation</a></li><li class="chapter-item expanded "><a href="../postgres.html">Using Postgres</a></li><li class="chapter-item expanded "><a href="../reverse_proxy.html">Configuring a Reverse Proxy</a></li><li class="chapter-item expanded "><a href="../setup/forward_proxy.html">Configuring a Forward/Outbound Proxy</a></li><li class="chapter-item expanded "><a href="../turn-howto.html">Configuring a Turn Server</a></li><li class="chapter-item expanded "><a href="../delegate.html">Delegation</a></li><li class="chapter-item expanded affix "><li class="part-title">Upgrading</li><li class="chapter-item expanded "><a href="../upgrade.html">Upgrading between Synapse Versions</a></li><li class="chapter-item expanded "><a href="../MSC1711_certificates_FAQ.html">Upgrading from pre-Synapse 1.0</a></li><li class="chapter-item expanded affix "><li class="part-title">Usage</li><li class="chapter-item expanded "><a href="../federate.html">Federation</a></li><li class="chapter-item expanded "><a href="../usage/configuration/index.html">Configuration</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="../usage/configuration/homeserver_sample_config.html">Homeserver Sample Config File</a></li><li class="chapter-item expanded "><a href="../usage/configuration/logging_sample_config.html">Logging Sample Config File</a></li><li class="chapter-item expanded "><a href="../structured_logging.html">Structured Logging</a></li><li class="chapter-item expanded "><a href="../templates.html">Templates</a></li><li class="chapter-item expanded "><a href="../usage/configuration/user_authentication/index.html">User Authentication</a></li><li><ol class="section"><li class="chapter-item expanded "><div>Single-Sign On</div></li><li><ol class="section"><li class="chapter-item expanded "><a href="../openid.html">OpenID Connect</a></li><li class="chapter-item expanded "><div>SAML</div></li><li class="chapter-item expanded "><div>CAS</div></li><li class="chapter-item expanded "><a href="../sso_mapping_providers.html">SSO Mapping Providers</a></li></ol></li><li class="chapter-item expanded "><a href="../password_auth_providers.html">Password Auth Providers</a></li><li class="chapter-item expanded "><a href="../jwt.html">JSON Web Tokens</a></li></ol></li><li class="chapter-item expanded "><a href="../CAPTCHA_SETUP.html">Registration Captcha</a></li><li class="chapter-item expanded "><a href="../application_services.html">Application Services</a></li><li class="chapter-item expanded "><a href="../server_notices.html">Server Notices</a></li><li class="chapter-item expanded "><a href="../consent_tracking.html">Consent Tracking</a></li><li class="chapter-item expanded "><a href="../development/url_previews.html">URL Previews</a></li><li class="chapter-item expanded "><a href="../user_directory.html">User Directory</a></li><li class="chapter-item expanded "><a href="../message_retention_policies.html">Message Retention Policies</a></li><li class="chapter-item expanded "><a href="../modules/index.html">Pluggable Modules</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="../modules/writing_a_module.html">Writing a module</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="../modules/spam_checker_callbacks.html">Spam checker callbacks</a></li><li class="chapter-item expanded "><a href="../modules/third_party_rules_callbacks.html">Third-party rules callbacks</a></li><li class="chapter-item expanded "><a href="../modules/presence_router_callbacks.html">Presence router callbacks</a></li><li class="chapter-item expanded "><a href="../modules/account_validity_callbacks.html">Account validity callbacks</a></li><li class="chapter-item expanded "><a href="../modules/password_auth_provider_callbacks.html">Password auth provider callbacks</a></li><li class="chapter-item expanded "><a href="../modules/porting_legacy_module.html">Porting a legacy module to the new interface</a></li></ol></li></ol></li><li class="chapter-item expanded "><a href="../workers.html">Workers</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="../synctl_workers.html">Using synctl with Workers</a></li><li class="chapter-item expanded "><a href="../systemd-with-workers/index.html">Systemd</a></li></ol></li></ol></li><li class="chapter-item expanded "><a href="../usage/administration/index.html">Administration</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="../usage/administration/admin_api/index.html">Admin API</a></li><li><ol class="section"><li class="chapter-item expanded "><a href="../admin_api/account_validity.html">Account Validity</a></li><li class="chapter-item expanded "><a href="../usage/administration/admin_api/background_updates.html">Background Updates</a></li><li class="chapter-item expanded "><a href="../admin_api/delete_group.html">Delete Group</a></li><li class="chapter-item expanded "><a href="../admin_api/event_reports.html">Event Reports</a></li><li class="chapter-item expanded "><a href="../admin_api/media_admin_api.html">Media</a></li><li class="chapter-item expanded "><a href="../admin_api/purge_history_api.html">Purge History</a></li><li class="chapter-item expanded "><a href="../admin_api/register_api.html">Register Users</a></li><li class="chapter-item expanded "><a href="../usage/administration/admin_api/registration_tokens.html">Registration Tokens</a></li><li class="chapter-item expanded "><a href="../admin_api/room_membership.html">Manipulate Room Membership</a></li><li class="chapter-item expanded "><a href="../admin_api/rooms.html">Rooms</a></li><li class="chapter-item expanded "><a href="../admin_api/server_notices.html">Server Notices</a></li><li class="chapter-item expanded "><a href="../admin_api/statistics.html">Statistics</a></li><li class="chapter-item expanded "><a href="../admin_api/user_admin_api.html">Users</a></li><li class="chapter-item expanded "><a href="../admin_api/version_api.html">Server Version</a></li></ol></li><li class="chapter-item expanded "><a href="../manhole.html">Manhole</a></li><li class="chapter-item expanded "><a href="../metrics-howto.html">Monitoring</a></li><li class="chapter-item expanded "><a href="../usage/administration/request_log.html">Request log format</a></li><li class="chapter-item expanded "><div>Scripts</div></li></ol></li><li class="chapter-item expanded "><li class="part-title">Development</li><li class="chapter-item expanded "><a href="../development/contributing_guide.html">Contributing Guide</a></li><li class="chapter-item expanded "><a href="../code_style.html">Code Style</a></li><li class="chapter-item expanded "><a href="../development/git.html" class="active">Git Usage</a></li><li class="chapter-item expanded "><div>Testing</div></li><li class="chapter-item expanded "><a href="../opentracing.html">OpenTracing</a></li><li class="chapter-item expanded "><a href="../development/database_schema.html">Database Schemas</a></li><li class="chapter-item expanded "><a href="../development/experimental_features.html">Experimental features</a></li><li class="chapter-item expanded "><div>Synapse Architecture</div></li><li><ol class="section"><li class="chapter-item expanded "><a href="../log_contexts.html">Log Contexts</a></li><li class="chapter-item expanded "><a href="../replication.html">Replication</a></li><li class="chapter-item expanded "><a href="../tcp_replication.html">TCP Replication</a></li></ol></li><li class="chapter-item expanded "><a href="../development/internal_documentation/index.html">Internal Documentation</a></li><li><ol class="section"><li class="chapter-item expanded "><div>Single Sign-On</div></li><li><ol class="section"><li class="chapter-item expanded "><a href="../development/saml.html">SAML</a></li><li class="chapter-item expanded "><a href="../development/cas.html">CAS</a></li></ol></li><li class="chapter-item expanded "><a href="../development/room-dag-concepts.html">Room DAG concepts</a></li><li class="chapter-item expanded "><div>State Resolution</div></li><li><ol class="section"><li class="chapter-item expanded "><a href="../auth_chain_difference_algorithm.html">The Auth Chain Difference Algorithm</a></li></ol></li><li class="chapter-item expanded "><a href="../media_repository.html">Media Repository</a></li><li class="chapter-item expanded "><a href="../room_and_user_statistics.html">Room and User Statistics</a></li></ol></li><li class="chapter-item expanded "><div>Scripts</div></li><li class="chapter-item expanded affix "><li class="part-title">Other</li><li class="chapter-item expanded "><a href="../deprecation_policy.html">Dependency Deprecation Policy</a></li></ol>
  75. </div>
  76. <div id="sidebar-resize-handle" class="sidebar-resize-handle"></div>
  77. </nav>
  78. <div id="page-wrapper" class="page-wrapper">
  79. <div class="page">
  80. <div id="menu-bar-hover-placeholder"></div>
  81. <div id="menu-bar" class="menu-bar sticky bordered">
  82. <div class="left-buttons">
  83. <button id="sidebar-toggle" class="icon-button" type="button" title="Toggle Table of Contents" aria-label="Toggle Table of Contents" aria-controls="sidebar">
  84. <i class="fa fa-bars"></i>
  85. </button>
  86. <button id="theme-toggle" class="icon-button" type="button" title="Change theme" aria-label="Change theme" aria-haspopup="true" aria-expanded="false" aria-controls="theme-list">
  87. <i class="fa fa-paint-brush"></i>
  88. </button>
  89. <ul id="theme-list" class="theme-popup" aria-label="Themes" role="menu">
  90. <li role="none"><button role="menuitem" class="theme" id="light">Light (default)</button></li>
  91. <li role="none"><button role="menuitem" class="theme" id="rust">Rust</button></li>
  92. <li role="none"><button role="menuitem" class="theme" id="coal">Coal</button></li>
  93. <li role="none"><button role="menuitem" class="theme" id="navy">Navy</button></li>
  94. <li role="none"><button role="menuitem" class="theme" id="ayu">Ayu</button></li>
  95. </ul>
  96. <button id="search-toggle" class="icon-button" type="button" title="Search. (Shortkey: s)" aria-label="Toggle Searchbar" aria-expanded="false" aria-keyshortcuts="S" aria-controls="searchbar">
  97. <i class="fa fa-search"></i>
  98. </button>
  99. <div class="version-picker">
  100. <div class="dropdown">
  101. <div class="select">
  102. <span></span>
  103. <i class="fa fa-chevron-down"></i>
  104. </div>
  105. <input type="hidden" name="version">
  106. <ul class="dropdown-menu">
  107. <!-- Versions will be added dynamically in version-picker.js -->
  108. </ul>
  109. </div>
  110. </div>
  111. </div>
  112. <h1 class="menu-title">Synapse</h1>
  113. <div class="right-buttons">
  114. <a href="../print.html" title="Print this book" aria-label="Print this book">
  115. <i id="print-button" class="fa fa-print"></i>
  116. </a>
  117. <a href="https://github.com/matrix-org/synapse" title="Git repository" aria-label="Git repository">
  118. <i id="git-repository-button" class="fa fa-github"></i>
  119. </a>
  120. <a href="https://github.com/matrix-org/synapse/edit/develop/docs/development/git.md" title="Suggest an edit" aria-label="Suggest an edit">
  121. <i id="git-edit-button" class="fa fa-edit"></i>
  122. </a>
  123. </div>
  124. </div>
  125. <div id="search-wrapper" class="hidden">
  126. <form id="searchbar-outer" class="searchbar-outer">
  127. <input type="search" id="searchbar" name="searchbar" placeholder="Search this book ..." aria-controls="searchresults-outer" aria-describedby="searchresults-header">
  128. </form>
  129. <div id="searchresults-outer" class="searchresults-outer hidden">
  130. <div id="searchresults-header" class="searchresults-header"></div>
  131. <ul id="searchresults">
  132. </ul>
  133. </div>
  134. </div>
  135. <!-- Apply ARIA attributes after the sidebar and the sidebar toggle button are added to the DOM -->
  136. <script type="text/javascript">
  137. document.getElementById('sidebar-toggle').setAttribute('aria-expanded', sidebar === 'visible');
  138. document.getElementById('sidebar').setAttribute('aria-hidden', sidebar !== 'visible');
  139. Array.from(document.querySelectorAll('#sidebar a')).forEach(function(link) {
  140. link.setAttribute('tabIndex', sidebar === 'visible' ? 0 : -1);
  141. });
  142. </script>
  143. <div id="content" class="content">
  144. <main>
  145. <!-- Page table of contents -->
  146. <div class="sidetoc">
  147. <nav class="pagetoc"></nav>
  148. </div>
  149. <h1 id="some-notes-on-how-we-use-git"><a class="header" href="#some-notes-on-how-we-use-git">Some notes on how we use git</a></h1>
  150. <h2 id="on-keeping-the-commit-history-clean"><a class="header" href="#on-keeping-the-commit-history-clean">On keeping the commit history clean</a></h2>
  151. <p>In an ideal world, our git commit history would be a linear progression of
  152. commits each of which contains a single change building on what came
  153. before. Here, by way of an arbitrary example, is the top of <code>git log --graph b2dba0607</code>:</p>
  154. <img src="img/git/clean.png" alt="clean git graph" width="500px">
  155. <p>Note how the commit comment explains clearly what is changing and why. Also
  156. note the <em>absence</em> of merge commits, as well as the absence of commits called
  157. things like (to pick a few culprits):
  158. <a href="https://github.com/matrix-org/synapse/commit/84691da6c">“pep8”</a>, <a href="https://github.com/matrix-org/synapse/commit/474810d9d">“fix broken
  159. test”</a>,
  160. <a href="https://github.com/matrix-org/synapse/commit/c9d72e457">“oops”</a>,
  161. <a href="https://github.com/matrix-org/synapse/commit/836358823">“typo”</a>, or <a href="https://github.com/matrix-org/synapse/commit/707374d5d">“Who's
  162. the president?”</a>.</p>
  163. <p>There are a number of reasons why keeping a clean commit history is a good
  164. thing:</p>
  165. <ul>
  166. <li>
  167. <p>From time to time, after a change lands, it turns out to be necessary to
  168. revert it, or to backport it to a release branch. Those operations are
  169. <em>much</em> easier when the change is contained in a single commit.</p>
  170. </li>
  171. <li>
  172. <p>Similarly, it's much easier to answer questions like “is the fix for
  173. <code>/publicRooms</code> on the release branch?” if that change consists of a single
  174. commit.</p>
  175. </li>
  176. <li>
  177. <p>Likewise: “what has changed on this branch in the last week?” is much
  178. clearer without merges and “pep8” commits everywhere.</p>
  179. </li>
  180. <li>
  181. <p>Sometimes we need to figure out where a bug got introduced, or some
  182. behaviour changed. One way of doing that is with <code>git bisect</code>: pick an
  183. arbitrary commit between the known good point and the known bad point, and
  184. see how the code behaves. However, that strategy fails if the commit you
  185. chose is the middle of someone's epic branch in which they broke the world
  186. before putting it back together again.</p>
  187. </li>
  188. </ul>
  189. <p>One counterargument is that it is sometimes useful to see how a PR evolved as
  190. it went through review cycles. This is true, but that information is always
  191. available via the GitHub UI (or via the little-known <a href="https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/checking-out-pull-requests-locally">refs/pull
  192. namespace</a>).</p>
  193. <p>Of course, in reality, things are more complicated than that. We have release
  194. branches as well as <code>develop</code> and <code>master</code>, and we deliberately merge changes
  195. between them. Bugs often slip through and have to be fixed later. That's all
  196. fine: this not a cast-iron rule which must be obeyed, but an ideal to aim
  197. towards.</p>
  198. <h2 id="merges-squashes-rebases-wtf"><a class="header" href="#merges-squashes-rebases-wtf">Merges, squashes, rebases: wtf?</a></h2>
  199. <p>Ok, so that's what we'd like to achieve. How do we achieve it?</p>
  200. <p>The TL;DR is: when you come to merge a pull request, you <em>probably</em> want to
  201. “squash and merge”:</p>
  202. <p><img src="img/git/squash.png" alt="squash and merge" />.</p>
  203. <p>(This applies whether you are merging your own PR, or that of another
  204. contributor.)</p>
  205. <p>“Squash and merge”<sup id="a1"><a href="#f1">1</a></sup> takes all of the changes in the
  206. PR, and bundles them into a single commit. GitHub gives you the opportunity to
  207. edit the commit message before you confirm, and normally you should do so,
  208. because the default will be useless (again: <code>* woops typo</code> is not a useful
  209. thing to keep in the historical record).</p>
  210. <p>The main problem with this approach comes when you have a series of pull
  211. requests which build on top of one another: as soon as you squash-merge the
  212. first PR, you'll end up with a stack of conflicts to resolve in all of the
  213. others. In general, it's best to avoid this situation in the first place by
  214. trying not to have multiple related PRs in flight at the same time. Still,
  215. sometimes that's not possible and doing a regular merge is the lesser evil.</p>
  216. <p>Another occasion in which a regular merge makes more sense is a PR where you've
  217. deliberately created a series of commits each of which makes sense in its own
  218. right. For example: <a href="https://github.com/matrix-org/synapse/pull/6837">a PR which gradually propagates a refactoring operation
  219. through the codebase</a>, or <a href="https://github.com/matrix-org/synapse/pull/5987">a
  220. PR which is the culmination of several other
  221. PRs</a>. In this case the ability
  222. to figure out when a particular change/bug was introduced could be very useful.</p>
  223. <p>Ultimately: <strong>this is not a hard-and-fast-rule</strong>. If in doubt, ask yourself “do
  224. each of the commits I am about to merge make sense in their own right”, but
  225. remember that we're just doing our best to balance “keeping the commit history
  226. clean” with other factors.</p>
  227. <h2 id="git-branching-model"><a class="header" href="#git-branching-model">Git branching model</a></h2>
  228. <p>A <a href="https://nvie.com/posts/a-successful-git-branching-model/">lot</a>
  229. <a href="http://scottchacon.com/2011/08/31/github-flow.html">of</a>
  230. <a href="https://www.endoflineblog.com/gitflow-considered-harmful">words</a> have been
  231. written in the past about git branching models (no really, <a href="https://martinfowler.com/articles/branching-patterns.html">a
  232. lot</a>). I tend to
  233. think the whole thing is overblown. Fundamentally, it's not that
  234. complicated. Here's how we do it.</p>
  235. <p>Let's start with a picture:</p>
  236. <p><img src="img/git/branches.jpg" alt="branching model" /></p>
  237. <p>It looks complicated, but it's really not. There's one basic rule: <em>anyone</em> is
  238. free to merge from <em>any</em> more-stable branch to <em>any</em> less-stable branch at
  239. <em>any</em> time<sup id="a2"><a href="#f2">2</a></sup>. (The principle behind this is that if a
  240. change is good enough for the more-stable branch, then it's also good enough go
  241. put in a less-stable branch.)</p>
  242. <p>Meanwhile, merging (or squashing, as per the above) from a less-stable to a
  243. more-stable branch is a deliberate action in which you want to publish a change
  244. or a set of changes to (some subset of) the world: for example, this happens
  245. when a PR is landed, or as part of our release process.</p>
  246. <p>So, what counts as a more- or less-stable branch? A little reflection will show
  247. that our active branches are ordered thus, from more-stable to less-stable:</p>
  248. <ul>
  249. <li><code>master</code> (tracks our last release).</li>
  250. <li><code>release-vX.Y</code> (the branch where we prepare the next release)<sup
  251. id="a3"><a href="#f3">3</a></sup>.</li>
  252. <li>PR branches which are targeting the release.</li>
  253. <li><code>develop</code> (our &quot;mainline&quot; branch containing our bleeding-edge).</li>
  254. <li>regular PR branches.</li>
  255. </ul>
  256. <p>The corollary is: if you have a bugfix that needs to land in both
  257. <code>release-vX.Y</code> <em>and</em> <code>develop</code>, then you should base your PR on
  258. <code>release-vX.Y</code>, get it merged there, and then merge from <code>release-vX.Y</code> to
  259. <code>develop</code>. (If a fix lands in <code>develop</code> and we later need it in a
  260. release-branch, we can of course cherry-pick it, but landing it in the release
  261. branch first helps reduce the chance of annoying conflicts.)</p>
  262. <hr />
  263. <p><b id="f1">[1]</b>: “Squash and merge” is GitHub's term for this
  264. operation. Given that there is no merge involved, I'm not convinced it's the
  265. most intuitive name. <a href="#a1">^</a></p>
  266. <p><b id="f2">[2]</b>: Well, anyone with commit access.<a href="#a2">^</a></p>
  267. <p><b id="f3">[3]</b>: Very, very occasionally (I think this has happened once in
  268. the history of Synapse), we've had two releases in flight at once. Obviously,
  269. <code>release-v1.2</code> is more-stable than <code>release-v1.3</code>. <a href="#a3">^</a></p>
  270. </main>
  271. <nav class="nav-wrapper" aria-label="Page navigation">
  272. <!-- Mobile navigation buttons -->
  273. <a rel="prev" href="../code_style.html" class="mobile-nav-chapters previous" title="Previous chapter" aria-label="Previous chapter" aria-keyshortcuts="Left">
  274. <i class="fa fa-angle-left"></i>
  275. </a>
  276. <a rel="next" href="../opentracing.html" class="mobile-nav-chapters next" title="Next chapter" aria-label="Next chapter" aria-keyshortcuts="Right">
  277. <i class="fa fa-angle-right"></i>
  278. </a>
  279. <div style="clear: both"></div>
  280. </nav>
  281. </div>
  282. </div>
  283. <nav class="nav-wide-wrapper" aria-label="Page navigation">
  284. <a rel="prev" href="../code_style.html" class="nav-chapters previous" title="Previous chapter" aria-label="Previous chapter" aria-keyshortcuts="Left">
  285. <i class="fa fa-angle-left"></i>
  286. </a>
  287. <a rel="next" href="../opentracing.html" class="nav-chapters next" title="Next chapter" aria-label="Next chapter" aria-keyshortcuts="Right">
  288. <i class="fa fa-angle-right"></i>
  289. </a>
  290. </nav>
  291. </div>
  292. <script type="text/javascript">
  293. window.playground_copyable = true;
  294. </script>
  295. <script src="../elasticlunr.min.js" type="text/javascript" charset="utf-8"></script>
  296. <script src="../mark.min.js" type="text/javascript" charset="utf-8"></script>
  297. <script src="../searcher.js" type="text/javascript" charset="utf-8"></script>
  298. <script src="../clipboard.min.js" type="text/javascript" charset="utf-8"></script>
  299. <script src="../highlight.js" type="text/javascript" charset="utf-8"></script>
  300. <script src="../book.js" type="text/javascript" charset="utf-8"></script>
  301. <!-- Custom JS scripts -->
  302. <script type="text/javascript" src="../docs/website_files/table-of-contents.js"></script>
  303. <script type="text/javascript" src="../docs/website_files/version-picker.js"></script>
  304. <script type="text/javascript" src="../docs/website_files/version.js"></script>
  305. </body>
  306. </html>