Platform for Mozilla Support
Перейти к файлу
Tasos Katsoulas 897e0723fc
Merge pull request #6261 from akatsoulas/validate-active-topics-products
Validate only active topic/products
2024-09-27 13:27:55 +03:00
.circleci
.devcontainer
.github - Updating playwright to 1.47.0 2024-09-13 14:18:50 +03:00
.vscode
bin
configs
docker
docs
jsi18n
kitsune Validate only active topic/products 2024-09-27 12:49:16 +03:00
media
playwright_tests - Mark the functions from the kb article discussions class as public and replace super() with self. 2024-09-26 23:47:20 +03:00
scripts
styleguide
svelte
webpack Moderate topics for forum questions 2024-09-25 11:42:14 +03:00
wsgi
.adr-dir
.dockerignore
.editorconfig
.env-build
.env-dist
.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 - Updating playwright to 1.47.0 2024-09-13 14:18:50 +03:00
postcss.config.js
pyproject.toml - Updating playwright to 1.47.0 2024-09-13 14:18:50 +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 ❤️