{"shas":[["b247f31f14d8300321b819a5461d9980ba9814c5","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Add documentation on optimizing MySQL and RB in general.\n\nThe MySQL docs cover query caching.\n\nThe general optimization tips talks about hardware recommendations and\nmulti-server strategies.","Christian Hammond"],["db4db1c5950b77c9bd8e63c99b279d0c830b66c5","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Rename \"Optimizing\" to \"Optimization.\"","Christian Hammond"],["6668793fed93a70491d19e1a6a7dcdfa67c8f7bc","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Rename the \"optimizing\" directory to \"optimization.\"","Christian Hammond"],["5a1b2f405d7e4357f16f38a8d6725486116e4d4f","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Reorder the Admin UI section before Configuration.","Christian Hammond"],["2312140a2ebc6a6923ddfbf0943cf1d67c68b9a1","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Add documentation on access control.\n\nThis covers the various settings for group and repository access control\non the Review Groups and Repository configuration pages, respectively. It also\nprovides a general Access Control page in the Configuration section, which\nsummarizes the options, points to the proper settings, and gives a summary of\nwhat conditions are required for a review request to be accessible to a user.\n\nFixes bug #2203","Christian Hammond"],["cf064ff4dec6d3df253df706b1d937500651a338","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Add documentation on reviewing file attachments.\n\nThis briefly talks about how to add comments to file attachments. It also\nincludes a screenshot of the file attachment box on both the Uploading File\nAttachments and reviewing File Attachments docs.\n\nFixes bug #2209","Christian Hammond"],["9d31d0a00382127109f7eb340ffae11ac04e5777","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Use the :mailheader: markup for the Sender and From headers.","Christian Hammond"],["90201d1d6e592615d71c1b17ab75d2364a871c63","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Don't fail on SSH tests when SSH isn't enabled.\n\nSSH tests were failing if the right keys existed but a local ssh daemon\nwasn't running. Now we treat a Connection Refused as an indication that\nwe should skip the test.","Christian Hammond"],["21c5eb6a440d7ba84fa449763333ede1affeb473","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Fix several broken links and directives.\n\nSeveral reference links were referencing docs with old-style reference rules,\nwhich don't work on the latest versions of Sphinx. These have been updated\nto use explicit anchors. There have also been a few that were just typoed.\n\nThere were also a couple 'note' directives that weren't structured correctly.","Christian Hammond"],["fdd59486f72c907fc69d27b5e7c14e8cf07f5f1e","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Add new glossary definitions for new terms.\n\nThis adds \"DKIM,\" \"local sites,\" and \"private review requests\" to the\nglossary, fixing several broken links.","Christian Hammond"],["6c8060f80acbe4d01e03f94cccf5efe49ff5d042","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Speed up unit tests by about 15%.\n\nA large part of the reason unit tests take so long is the loading of the\nfixtures. Specifically, all the review request fixtures. However, many tests\ndon't even need all the fixtures that their class loads.\n\nBy making use of the new TestCase class and @add_fixtures decorator in Djblets,\nwe can be more specific about what fixtures are used where.\n\nSeveral TestCase classes have been updated to only include the bare minimum\nset of fixtures defined in the class, with individual tests listing the\nother more specific fixtures they need.\n\nThrough this and some other improvements, I've shaved over 30 seconds from my\nunit test run. That's a savings of about 15%.\n\nThere's still more we can do here. The test_reviewrequests fixture is the\nbiggest fixture, and most of what it contains should probably be split out.\nA good first step is to move all the site-specific ones out into another\nfixture. Without this, you need to include both test_reviewrequests and\ntest_site in order to properly load in review requests to test with, even\nif we aren't testing with a site (since otherwise, those review requests come\nin with a local_site as None).\n\nWe can also split out the review groups and changes into their own fixtures.\nMany tests are really testing against those and don't need the full list of\nreview requests.","Christian Hammond"],["501c141004aad09d9fc354b24b71cb4302dd65a3","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Use introspection to generate our error docs.\n\nThe error docs, like the resource docs, are now generated through\nintrospection. Each file uses a \"webapierror\" directive, listing the\nerror instance, a description, and optionally a title or example data for\nthe error payloads.\n\nThis should keep the docs up-to-date for the most part as error text changes.","Christian Hammond"],["816fde80c468f18537b0297cbd33af5418134c9b","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Rename \"Reviewing Files\" back to \"Reviewing\"","Christian Hammond"],["679c54278212509277f6d2c1d832fc4733dbd12a","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Add documentation on issue tracking.\n\nFixes bug #2202","Christian Hammond"],["eb19d38605156f75c84c8e0533e7bf287132259f","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Fix and polish drag-and-drop on Firefox and Chrome.\n\nDrag-and-drop had some issues due to how we handled the various events.\nHTML5 drag events are a bit strange and don't act as one would expect, mostly\nbecause of legacy IE reasons. You can't easily determine through the event\nif the dragleave was due to leaving the window. In the case of Firefox 4+,\ndragleave won't even fire if leaving a window.\n\nThe code is now simplified to only listen for dragleave on the drop indicator\noverlay. If we get it, we compare the coordinates for where the leave took\nplace. Generally, this will be 0 if we exit, with the exception of the\nright-hand-side scrollbar, where we need to compare with the page width. Using\nthis information, we can know with more certainty that the user dragged outside\nthe browser.\n\nFirefox will still be stuck with the drag screen, but the workaround there is\nto listen for mouse movement over the drop indicator. If that indicator is\non the screen, the only way mouse movement will be recorded is if a drop isn't\nin progress. We schedule a drag exit in this case.\n\nThis also adds a nice fadeout instea of an immediate removal of the indicator.\n\nFixes bug #2196","Christian Hammond"],["73c6b21780b47ec39b49c81693b9e7d08b98a2de","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Add support for issue tracking to file attachment comments.\n\nFile attachment comments never received support for issue tracking in the past.\nThe dialog showed the \"Open an issue\" checkbox, but it would fail if checked.\n\nThe resources and UI have all now been updated to pass the issue tracking\nstate around. Now, file attachment comments can have issues filed, and those\nissues can be resolved, dropped, or re-opened like any others.","Christian Hammond"],["755bcaab9e0c48540ebb47d90571e5fd2a02a244","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Enable issue tracking by default, and add an alt-I shortcut.\n\nMore often than not, I believe people will want issue tracking enabled, but\nit's annoying to click the checkbox every time.\n\nThis change defaults issue tracking to on by default, which appears to have\nbeen the original intent in the HTML.\n\nUsers can turn issue tracking off quickly by pressing Alt-I in the textbox.\n\nDocumentation has been updated to reflect these changes.","Christian Hammond"],["810708086fb44ec3502036dd9e031ac5fe2340b5","a3e5bf1e23f9b398fd796b3f030b30fdb8b825f9@chipx86.com","Add anchors for several doc pages used in the release notes.","Christian Hammond"]],"ref":"refs/heads/master","size":18,"head":"810708086fb44ec3502036dd9e031ac5fe2340b5","push_id":41736296}