You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,6 @@ There are other branches available which serve specific purposes.
19
19
20
20
| Branch | Purpose |
21
21
| ------ | ------- |
22
-
| staging | Current codebase. Branch for the next minor Joomla version. New backward compatible features go into this branch. |
23
-
| master | Each commit made to staging gets tested if it passes unit tests and codestyle rules. It is then merged into master. This is done automatically. |
24
-
| 3.8-dev | Branch for the next minor Joomla version. The 3.8.0 release will only include compatibility features for 4.0. Commits to staging will be applied to this branch as well. |
22
+
| staging | Current codebase. Branch for the next minor Joomla version. New backward compatible features go into this branch. The 3.9.0 release will include the Privacy Tools Suite features. |
23
+
| 3.10-dev | Branch for the next minor Joomla version. The 3.10.0 release will only include compatibility features for 4.0. Commits to staging will be applied to this branch as well. |
25
24
| 4.0-dev | Branch for the next major Joomla version. New features go into this branch. Commits to staging will be applied to this branch as well. |
Security issues should **NOT** be reported on this repository.
8
+
9
+
If you believe you have found a security issue, please contact the Joomla Security Strike Team via email at [email protected] or through the contact form at https://developer.joomla.org/security/contact-the-team.html.
10
+
11
+
Please see https://developer.joomla.org/security.html for more information on how the Joomla project responds to security issues.
*[Further Details on the Joomla! Security Policies](https://security.joomla.org)
9
+
10
+
## Reporting a Bug
11
+
12
+
The `Joomla` team and community take all security bugs in `Joomla` seriously. The Joomla! Security Strike Team (JSST) oversees the project's security issues and follows some specific procedures when dealing with these issues.
13
+
14
+
If you find a possible vulnerability, please report it to the JSST using the [online form](https://developer.joomla.org/security/contact-the-team.html) or via email at [email protected]
15
+
16
+
We maintain a list of [GPG keys and addresses](https://developer.joomla.org/security/gpg-keys.html) for the [email protected] address and members of the JSST to allow signed and encrypted communications.
17
+
18
+
To report an issue in a Joomla! extension, please submit it to the [Vulnerable Extensions List.](https://vel.joomla.org/submit-vel)
19
+
20
+
For support with a site which has been attacked, please visit the [Joomla! Forum.](https://forum.joomla.org/viewforum.php?f=714)
21
+
22
+
Thank you for improving the security of `Joomla`.
23
+
24
+
## Response Handling
25
+
26
+
The JSST aims to ensure all issues are handled in a timely manner and for clear communication between the team and issue reporters. We have established the following guidelines for responding to issue reports:
27
+
28
+
* Within 24 hours every report gets acknowledged
29
+
* Within 7 days every report gets a further response stating either
30
+
* the issue is closed (and why)
31
+
* the issue is still under investigation; if needed, additional information will be requested
32
+
* Within 21 days every report must be resolved unless there are exceptional circumstances requiring additional time
33
+
34
+
## Security Announcement Policy
35
+
* Verified vulnerabilities will only be publicly announced AFTER a release is issued which fixes the vulnerability.
36
+
* All announcements will contain as much information as possible, but will NOT contain step-by-step instructions for the vulnerability.
37
+
* The `Joomla! Project` will properly credit individuals and/or organizations who responsibly disclose security issues to the JSST. You can indicate the way you would like to be referred to in the advisory about the vulnerability. Our preference is to use full names. If you do not specify then we will use the contact name associated with the email address the report was received from. You can also request a pseudonym or having your name withheld.
0 commit comments