mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-11-20 11:36:04 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Added backticks to email addresses in docs.
Some checks are pending
Docs / spelling (push) Waiting to run
Details
Docs / blacken-docs (push) Waiting to run
Details
Docs / lint-docs (push) Waiting to run
Details
Linters / flake8 (push) Waiting to run
Details
Linters / isort (push) Waiting to run
Details
Linters / black (push) Waiting to run
Details
Tests / Windows, SQLite, Python 3.13 (push) Waiting to run
Details
Tests / JavaScript tests (push) Waiting to run
Details

Browse source
This commit is contained in:
Mariusz Felisiak 2025-09-17 22:23:57 +02:00 • committed by GitHub
parent cebbd5a6ad
commit f8d2610d94
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
7 changed files with 19 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/internals/contributing/bugs-and-features.txt
View file

@ -5,7 +5,7 @@ Reporting bugs and requesting features
.. Important::
Please report security issues **only** to
security@djangoproject.com. This is a private list only open to
``security@djangoproject.com``. This is a private list only open to
long-time, highly trusted Django developers, and its archives are
not public. For further details, please see :doc:`our security
policies </internals/security>`.

9
docs/internals/howto-release-django.txt
View file

@ -650,10 +650,11 @@ Now you're ready to actually put the release out there. To do this:
Django Forum. This should include a link to the announcement blog post.
#. If this is a security release, send a separate email to
oss-security@lists.openwall.com. Provide a descriptive subject, for example,
"Django" plus the issue title from the release notes (including CVE ID). The
message body should include the vulnerability details, for example, the
announcement blog post text. Include a link to the announcement blog post.
``oss-security@lists.openwall.com``. Provide a descriptive subject, for
example, "Django" plus the issue title from the release notes (including CVE
ID). The message body should include the vulnerability details, for example,
the announcement blog post text. Include a link to the announcement blog
post.
Post-release
============

2
docs/internals/mailing-lists.txt
View file

@ -5,7 +5,7 @@ Mailing lists and Forum
.. Important::
Please report security issues **only** to
security@djangoproject.com. This is a private list only open to
``security@djangoproject.com``. This is a private list only open to
long-time, highly trusted Django developers, and its archives are
not public. For further details, please see :doc:`our security
policies </internals/security>`.