Platform for Mozilla Support
Перейти к файлу
Ryan Johnson 18c7daabf3
Merge pull request #6207 from escattone/fix-1783
fix contributor tools menus on mobile
2024-08-30 08:33:02 -07:00
.circleci
.devcontainer
.github Update docs workflow caching 2024-08-11 21:40:36 +02:00
.vscode
bin
configs
docker
docs Use internal IA for the AAQ instead of a config. 2024-08-08 09:27:56 -07:00
jsi18n
kitsune fix contributor tools menus on mobile 2024-08-30 07:37:21 -07:00
media
playwright_tests - Fix waits & test errors. 2024-08-22 21:53:43 +03:00
scripts
styleguide
svelte
webpack
wsgi
.adr-dir
.dockerignore
.editorconfig
.env-build
.env-dist Use django-silk for profiling 2024-08-16 16:51:33 +03:00
.env-test
.eslintrc
.gitignore
.nvmrc
.pre-commit-config.yaml
.stylelintrc
CODE_OF_CONDUCT.md
CONTRIBUTORS.rst
Dockerfile
LICENSE
Makefile
README.md
babel.cfg
babeljs.cfg
contribute.json
docker-compose.yml
manage.py
mkdocs.yml
newrelic.ini
package-lock.json
package.json
poetry.lock - Update playwright to 1.46 2024-08-21 13:38:26 +03:00
postcss.config.js
pyproject.toml - Update playwright to 1.46 2024-08-21 13:38:26 +03:00
setup.cfg
webpack.common.js
webpack.dev.js
webpack.pre-render.js
webpack.prod.js
webpack.test.js

README.md

Kitsune

Status Sustain

Kitsune is the platform that powers SuMo (support.mozilla.org)

Usage

It is a Django application. There is documentation online.

Releasing a new version

  • Create a signed tag for the new version.

    We are using semantic versioning.

    Given a version number MAJOR.MINOR.PATCH, increment the:

    MAJOR version when you make incompatible API changes
    MINOR version when you add functionality in a backward compatible manner
    PATCH version when you make backward compatible bug fixes
    

    Example:

    git tag -s 1.0.1 -m "Bump version: 1.0.0 to 1.0.1

  • Draft a new release in GitHub for the new tag. Document the highlights of the release and also use the option to automatically document the release through the commit history.

  • Trigger the release for the specified tag in the deploy repository.

[!TIP] You can access the staging site at https://support.allizom.org/.

Code of Conduct

By participating in this project, you're agreeing to uphold the Mozilla Community Participation Guidelines. If you need to report a problem, please see our Code of Conduct guide.

Contribute

See our contribution guide, or dive into setting up your development environment.

Issues

We use Bugzilla for submitting and prioritizing issues.

Thanks to all of our contributors ❤️