Confirmed users
2,473
edits
| Line 13: | Line 13: | ||
# <b>Stable URLs</b> - Hosting with GitHub.com decreases control over our repository URLs. We want stable URLs for linking in Bugzilla, pushlog, and elsewhere. (For more information see [[SCM/GitHubFAQ#Why_aren.E2.80.99t_GitHub_URLs_stable.3F|Why aren't GitHub URLs stable?]]) | # <b>Stable URLs</b> - Hosting with GitHub.com decreases control over our repository URLs. We want stable URLs for linking in Bugzilla, pushlog, and elsewhere. (For more information see [[SCM/GitHubFAQ#Why_aren.E2.80.99t_GitHub_URLs_stable.3F|Why aren't GitHub URLs stable?]]) | ||
# <b>Network availability and latency</b> - This has been a problem causing build failures over the last year. This problem can be mitigated with internal mirrors but this increases the complexity for the releng team and requires running a Mozilla instance of Git. (For more information see [[SCM/GitHubFAQ#Can_we_pay_GitHub_for_improved_availability.3F|Can we pay GitHub for improved availability?]]) | # <b>Network availability and latency</b> - This has been a problem causing build failures over the last year. This problem can be mitigated with internal mirrors but this increases the complexity for the releng team and requires running a Mozilla instance of Git. (For more information see [[SCM/GitHubFAQ#Can_we_pay_GitHub_for_improved_availability.3F|Can we pay GitHub for improved availability?]]) | ||
# <b>Limited permission support</b> - This impacts our ability to limit commit access to portions of the | # <b>Limited permission support</b> - This impacts our ability to limit commit access to portions of the tree. (For more information see [[SCM/GitHubFAQ#What_are_the_limitations_of_GitHub.E2.80.99s_permission_system.3F|What are the limitations of GitHub's permission system?]]) | ||
==What is the issue with post-receive hooks? Can we achieve the same functionality as we have with Hg?== | ==What is the issue with post-receive hooks? Can we achieve the same functionality as we have with Hg?== | ||