Chris Cooper [:coop] (he/him) Reporter
	Description • 9 years ago

This is very appealing because it means we can leverage (and augment) the existing travis testing support for releng repos in github. Having travis testing running automatically on user forks should lead to improved code quality and induce less churn when patches merge to production.

https://wiki.mozilla.org/ReleaseEngineering/Repositories will give us a list of repos that will need to move. 

Known dependencies:
* figure out how this affects tagging for releases
* reverse the current VCS sync processes that mirror from hg -> github
* update services (e.g. buildbot-masters) that currently pull from hg to pull from github instead <- provided the VCS sync is still in place, this can wait or be dropped

	Chris Cooper [:coop] (he/him) Reporter
	Comment 1 • 9 years ago

(In reply to Chris Cooper [:coop] from comment #0)
> This is very appealing because it means we can leverage (and augment)

Filed bug 1140421 to include builder list and dump_masters diff output in travis.