head	1.2;
access;
symbols
	RELENG_4_11_0_RELEASE:1.1.2.2
	RELENG_4_11:1.1.2.2.0.16
	RELENG_4_11_BP:1.1.2.2
	RELENG_4_10_0_RELEASE:1.1.2.2
	RELENG_4_10:1.1.2.2.0.14
	RELENG_4_10_BP:1.1.2.2
	RELENG_4_9_0_RELEASE:1.1.2.2
	RELENG_4_9:1.1.2.2.0.12
	RELENG_4_9_BP:1.1.2.2
	RELENG_4_8_0_RELEASE:1.1.2.2
	RELENG_4_8:1.1.2.2.0.10
	RELENG_4_8_BP:1.1.2.2
	RELENG_4_7_0_RELEASE:1.1.2.2
	RELENG_4_7:1.1.2.2.0.8
	RELENG_4_7_BP:1.1.2.2
	RELENG_4_6_2_RELEASE:1.1.2.2
	RELENG_4_6_1_RELEASE:1.1.2.2
	RELENG_4_6_0_RELEASE:1.1.2.2
	RELENG_4_6:1.1.2.2.0.6
	RELENG_4_6_BP:1.1.2.2
	RELENG_4_5_0_RELEASE:1.1.2.2
	RELENG_4_5:1.1.2.2.0.4
	RELENG_4_5_BP:1.1.2.2
	RELENG_4_4_0_RELEASE:1.1.2.2
	RELENG_4_4:1.1.2.2.0.2
	RELENG_4_4_BP:1.1.2.2
	RELENG_4:1.1.0.2;
locks; strict;
comment	@# @;


1.2
date	2001.06.11.01.48.13;	author ache;	state dead;
branches;
next	1.1;

1.1
date	2001.04.27.21.27.55;	author bmah;	state Exp;
branches
	1.1.2.1;
next	;

1.1.2.1
date	2001.06.01.18.02.56;	author bmah;	state Exp;
branches;
next	1.1.2.2;

1.1.2.2
date	2001.06.22.00.29.20;	author bmah;	state dead;
branches;
next	;


desc
@@


1.2
log
@ISO_* -> ISO* rename
@
text
@<!--

$FreeBSD: src/release/doc/en_US.ISO_8859-1/readme/problems.sgml,v 1.1 2001/04/27 21:27:55 bmah Exp $

problems.sgml

Information on contacting the FreeBSD project, originally from
RELNOTES.TXT.

-->

<sect1 id="contacting">
  <title>Reporting Problems, Making Suggestions, and Submitting
  Code</title>

  <para>Your suggestions, bug reports and contributions of code are
  always valued &mdash; please do not hesitate to report any problems you
  may find (preferably with a fix attached, if you can!).</para>

  <para>The preferred method to submit bug reports from a machine with
  Internet mail connectivity is to use the &man.send-pr.1; command or
  use the CGI script at <ulink
  url="http://www.FreeBSD.org/send-pr.html">http://www.FreeBSD.org/send-pr.html</ulink>.
  Bug reports will be dutifully filed by our faithful bugfiler program
  and you can be sure that we'll do our best to respond to all
  reported bugs as soon as possible.  Bugs filed in this way are also
  visible on our Web site in the support section and are therefore
  valuable both as bug reports and as <quote>signposts</quote> for
  other users concerning potential problems to watch out for.</para>

  <para>If, for some reason, you are unable to use &man.send-pr.1; to
  submit a bug report, you can try to send it to the &a.bugs;.</para>

  <para>Note that &man.send-pr.1; itself is a shell script that should
  be easy to move even onto a totally different system.  We much
  prefer if you could use this interface, since it make it easier to
  keep track of the problem reports.  However, before submitting,
  please try to make sure whether the problem might have already been
  fixed since.</para>

  <para>Otherwise, for any questions or tech support issues, please send
  mail to the &a.questions;.</para>

  <para>If you're tracking the -current development efforts, you
  <emphasis>must</emphasis> join the &a.current;, in order to keep
  abreast of recent developments and changes that may affect the way
  you use and maintain the system.

  <para>Additionally, being a volunteer effort, we are always happy to
  have extra hands willing to help &mdash; there are already far more
  desired enhancements than we'll ever be able to manage by ourselves!
  To contact us on technical matters, or with offers of help, please
  send mail to the &a.hackers;.</para>

  <para>Please note that these mailing lists can experience
  <emphasis>significant</emphasis> amounts of traffic and if you have
  slow or expensive mail access and are only interested in keeping up
  with significant FreeBSD events, you may find it preferable to
  subscribe instead to the &a.announce;.</para>

  <para>All of the mailing lists can be freely joined by anyone
  wishing to do so.  Send mail to &a.majordomo;
  and include the keyword <literal>help</literal> on a line by itself
  somewhere in the body of the message.  This will give you more
  information on joining the various lists, accessing archives, etc.
  There are a number of mailing lists targeted at special interest
  groups not mentioned here; more information can be obtained either
  through majordomo or the <ulink
  url="http://www.freebsd.org/support.html#mailing-list">mailing lists
  section</ulink> of the FreeBSD Web site.</para>

  <important>
  <para>Do <emphasis>not</emphasis> send email to the lists asking to
  be subscribed.  Use the &a.majordomo; address
  instead.</para>
  </important>

</sect1>
@


1.1
log
@First commit of RELNOTESng, the rewrite of the *.TXT documentation
files.

src/release/doc/README has additional information.

Reviewed by:	-current, -doc
@
text
@d3 1
a3 1
$FreeBSD$
@


1.1.2.1
log
@MFC:  RELNOTESng.

I didn't MFC the changes to the release Makefile or the nuking of the
*.TXT files.  We're not ready for that yet.  I just wanted to get the
RELNOTESng sources for RELENG_4 into the repository so I can maintain
the content in parallel with the *.TXT version of the release notes.

These files include an SGML-ified version of RELENG_4's release notes,
plus the hardware compatability lists from HEAD (minus
CURRENT-specific features such as Cardbus support).
@
text
@d3 1
a3 1
$FreeBSD: src/release/doc/en_US.ISO_8859-1/readme/problems.sgml,v 1.1 2001/04/27 21:27:55 bmah Exp $
d44 2
a45 2
  <para>If you're tracking the -stable development efforts, you
  <emphasis>must</emphasis> join the &a.stable;, in order to keep
@


1.1.2.2
log
@MFC:  ISO_* -> ISO* rename.
@
text
@d3 1
a3 1
$FreeBSD: src/release/doc/en_US.ISO_8859-1/readme/problems.sgml,v 1.1.2.1 2001/06/01 18:02:56 bmah Exp $
@