diff options
Diffstat (limited to 'rt/docs')
| -rw-r--r-- | rt/docs/UPGRADING.mysql | 6 | ||||
| -rw-r--r-- | rt/docs/customizing/styling_rt.pod | 3 | ||||
| -rw-r--r-- | rt/docs/hacking.pod | 8 | ||||
| -rw-r--r-- | rt/docs/security.pod | 4 |
4 files changed, 16 insertions, 5 deletions
diff --git a/rt/docs/UPGRADING.mysql b/rt/docs/UPGRADING.mysql index b0e6cc367..8a39cd330 100644 --- a/rt/docs/UPGRADING.mysql +++ b/rt/docs/UPGRADING.mysql @@ -104,8 +104,10 @@ NOTE that 'rt3' is the default name of the RT database, change it in the command above if your database is named differently. This step should not produce any errors or warnings. If you see any, restore -your database from the backup you made at step 1, and send a report to the -rt-users@lists.bestpractical.com mailing list. +your database from the backup you made at step 1 and examine the errors to +determine the cause. Consult your DBA for MySQL-specific issues. For RT +issues, you can post to the community forum at L<https://forum.bestpractical.com> +for help or send email to sales@bestpractical.com for professional assistance. =item 8. diff --git a/rt/docs/customizing/styling_rt.pod b/rt/docs/customizing/styling_rt.pod index 7e37d009e..1647396d6 100644 --- a/rt/docs/customizing/styling_rt.pod +++ b/rt/docs/customizing/styling_rt.pod @@ -121,6 +121,9 @@ started: $ mkdir -p local/static/css/localstyle $ cp -R share/static/css/rudder/* local/static/css/localstyle/ + $ mkdir -p local/html/NoAuth/css/localstyle + $ cp -R share/html/NoAuth/css/rudder/* local/html/NoAuth/css/localstyle/ + You can call your "localstyle" directory whatever you want and you don't have to copy the rudder theme to start from, but it's a good place to start off for RT4. diff --git a/rt/docs/hacking.pod b/rt/docs/hacking.pod index 23ce51e3a..e254665e2 100644 --- a/rt/docs/hacking.pod +++ b/rt/docs/hacking.pod @@ -204,6 +204,11 @@ before the fix and succeeds after. =head1 git quickstart +The process below describes how to get a copy of an RT repo, +modify it, and submit your changes as a patch. You can also create +an account on GitHub, fork RT, and submit a PR. GitHub has documentation +on this process: L<https://help.github.com/articles/fork-a-repo/>. + =over =item 1. @@ -299,7 +304,8 @@ This will print out the names of the files as it creates them. =item 9. Attach these files to an email using your standard email client, and -send it to C<rt-devel@bestpractical.com>. +send it to C<rt-bugs@bestpractical.com>. This will create a ticket in +our public RT instance at L<https://issues.bestpractical.com>. =back diff --git a/rt/docs/security.pod b/rt/docs/security.pod index 5bf42919c..7120e389a 100644 --- a/rt/docs/security.pod +++ b/rt/docs/security.pod @@ -16,8 +16,8 @@ After a security vulnerability is reported to Best Practical and verified, we attempt to resolve it in as timely a fashion as possible. Best Practical support customers will be notified before we disclose the information to the public. All security announcements will be sent to -C<rt-announce@bestpractical.com>, which includes -C<rt-users@bestpractical.com> and C<rt-devel@bestpractical.com>. +C<rt-announce@bestpractical.com> and posted to the community forum at +L<https://forum.bestpractical.com> As the tests for security vulnerabilities are often nearly identical to working exploits, sensitive tests will be embargoed for a period of six |