mozilla-releng / addonscript Goto Github PK

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to [email protected].

(Message COC001)

The production branch on this repository is not protected against force pushes. This setting is recommended as part of Mozilla's Guidelines for a Sensitive Repository.

Anyone with admin permissions for this repository can correct the setting using this URL.

If you have any questions, or believe this issue was opened in error, please contact us and mention SOGH0001 and this repository.

Thank you for your prompt attention to this issue.
--Firefox Security Operations team

So, with the requirements bump of yarl, we now require at least python 3.5.3, this can be reverted but isn't a big deal atm. Since our deployment will soon use 3.6.x but means I can't bump pinned versions from here to make our deployment match up just yet.

• Use Docker & Docker Compose for running a local dev environment, based on the python:3 image
• Use pip-compile-multi, and Pyup.io for dependency management
  • See https://github.com/mozilla-releng/releng-rfcs/blob/master/rfcs/0022-app-best-practices.md#dependency-management for requirements file details.
• Use tox as a test runner
• Use Taskcluster for CI
• Ensure production pushes happen manually, in response to bugs filed
• Ensure stage pushes happen in response to balrog_stage tags on Dockerhub
• Eliminate the development environment, if it exists