[Rt-commit] rt branch, 4.0/remove-mailing-list-references, created. rt-4.0.24-46-g8e226e9
Jim Brandt
jbrandt at bestpractical.com
Fri May 19 10:53:05 EDT 2017
The branch, 4.0/remove-mailing-list-references has been created
at 8e226e9f92abf2118de89936f4c42c8c6b5e1640 (commit)
- Log -----------------------------------------------------------------
commit 8e226e9f92abf2118de89936f4c42c8c6b5e1640
Author: Jim Brandt <jbrandt at bestpractical.com>
Date: Fri May 19 10:52:54 2017 -0400
Update references to inactive mailing lists
diff --git a/docs/UPGRADING.mysql b/docs/UPGRADING.mysql
index b0e6cc3..8a39cd3 100644
--- a/docs/UPGRADING.mysql
+++ b/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 at 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 at bestpractical.com for professional assistance.
=item 8.
diff --git a/docs/hacking.pod b/docs/hacking.pod
index 7c50ee9..2051572 100644
--- a/docs/hacking.pod
+++ b/docs/hacking.pod
@@ -198,6 +198,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.
@@ -293,7 +298,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 at bestpractical.com>.
+send it to C<rt-bugs at bestpractical.com>. This will create a ticket in
+our public RT instance at L<https://issues.bestpractical.com>.
=back
diff --git a/docs/security.pod b/docs/security.pod
index 620f868..e774be5 100644
--- a/docs/security.pod
+++ b/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 at bestpractical.com>, which includes
-C<rt-users at bestpractical.com> and C<rt-devel at bestpractical.com>.
+C<rt-announce at 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
diff --git a/lib/RT.pm b/lib/RT.pm
index 851508a..6ea6e79 100644
--- a/lib/RT.pm
+++ b/lib/RT.pm
@@ -862,7 +862,9 @@ sub StyleSheets {
Please report them to rt-bugs at bestpractical.com, if you know what's
broken and have at least some idea of what needs to be fixed.
-If you're not sure what's going on, report them rt-devel at lists.bestpractical.com.
+If you're not sure what's going on, start a discussion in the RT Developers
+category on the community forum at L<https://forum.bestpractical.com> or
+send email to sales at bestpractical.com for professional assistance.
=head1 SEE ALSO
diff --git a/lib/RT/StyleGuide.pod b/lib/RT/StyleGuide.pod
index 8fdfc7b..146c683 100644
--- a/lib/RT/StyleGuide.pod
+++ b/lib/RT/StyleGuide.pod
@@ -20,7 +20,8 @@ degree to any Perl code written for use in RT.
Note that these are all guidelines, not unbreakable rules. If you have
a really good need to break one of the rules herein, however, then it is
-best to ask on the B<rt-devel> mailing list first.
+best to first start a discussion in the RT Developers category on the community
+forum at L<https://forum.bestpractical.com>.
Note that with much of this document, it is not so much the Right Way as
it is Our Way. We need to have conventions in order to make life easier
@@ -28,10 +29,6 @@ for everyone. So don't gripe, and just follow it, because you didn't
get a good grade in "Plays Well With Others" in kindergarten and you
want to make up for it now.
-If you have any questions, please ask us on the B<rt-devel> mailing list:
-
- http://www.bestpractical.com/rt/lists.html
-
We don't always follow this guide. We are making changes throughout
our code to be in line with it. But just because we didn't do
it yet, that is no excuse. Do it anyway. :-)
@@ -724,7 +721,7 @@ This is for new programs, modules, specific APIs, or anything else.
=over 4
-=item Present idea to rt-devel
+=item Create a topic in RT Developers on the Forum
We may know of a better way to approach the problem, or know of an
existing way to deal with it, or know someone else is working on it.
@@ -732,11 +729,11 @@ This is mostly informal, but a fairly complete explanation for the need
and use of the code should be provided.
-=item Present complete specs to rt-devel
+=item Present specs in RT Developers
The complete proposed API should be submitted for
-approval and discussion. For web and command-line programs, present the
-functionality and interface (op codes, command-lin switches, etc.).
+discussion. For web and command-line programs, present the
+functionality and interface (op codes, command-line switches, etc.).
The best way to do this is to take the documentation portion of the
boilerplate and fill it in. You can make changes later if necessary,
@@ -761,9 +758,10 @@ guide contained in this document.
=item Finish it up
After the code is done (possibly going through multiple code reviews),
-if you do not have repository access, submit it to rt-bugs at fsck.com as a
-unified diff. From that point on, it'll be handled by someone with
-repository access.
+submit your updates as a pull request on GitHub. If you don't have a GitHub
+account, you can generate patches and send email to rt-bugs at bestpractical.com
+which will create a ticket in our public issue tracker at
+L<https://issues.bestpractical.com>.
=back
-----------------------------------------------------------------------
More information about the rt-commit
mailing list