Date: Sat, 2 Feb 2002 00:00:05 -0800 (PST) From: Jay Edwards <jayed@jayed.com> To: freebsd-doc@freebsd.org Subject: Re:docs/34547: [patch] edits of FAQ Introduction Message-ID: <200202020800.g12805434363@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR docs/34547; it has been noted by GNATS. From: Jay Edwards <jayed@jayed.com> To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re:docs/34547: [patch] edits of FAQ Introduction Date: Sat, 2 Feb 2002 01:56:47 -0600 (Oops. Forgot the patch). Index: book.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/faq/book.sgml,v retrieving revision 1.400 diff -c -r1.400 book.sgml *** book.sgml 2002/02/02 00:43:51 1.400 --- book.sgml 2002/02/02 06:15:14 *************** *** 225,244 **** </listitem> <listitem> ! <para>Anyone who has an improvement and/or bug fix is free to submit their code and have it added to the source tree (subject to one or two obvious provisions).</para> </listitem> </itemizedlist> ! <para>For those of our readers whose first language is not ! English, it may be worth pointing out that the word ! <quote>free</quote> is being used in two ways here, one meaning ! <quote>at no cost</quote>, the other meaning <quote>you can do ! whatever you like</quote>. Apart from one or two things you ! <emphasis>cannot</emphasis> do with the FreeBSD code, for ! example pretending you wrote it, you really can do whatever you ! like with it.</para> </answer> </qandaentry> --- 225,242 ---- </listitem> <listitem> ! <para>Anyone who has an improvement or bug fix is free to submit their code and have it added to the source tree (subject to one or two obvious provisions).</para> </listitem> </itemizedlist> ! <para>It is worth pointing out that the word <quote>free</quote> ! is being used in two ways here, one meaning <quote>at no cost ! </quote>, the other meaning <quote>you can do whatever you like ! Apart from one or two things you <emphasis>cannot</emphasis> ! do with the FreeBSD code (for example, pretending that you ! wrote it, you can do whatever you like with it.</para> </answer> </qandaentry> *************** *** 254,270 **** released in &rel.current.date;. This is also the latest <emphasis>RELEASE</emphasis> version.</para> ! <para>Briefly explained, <emphasis>-STABLE</emphasis> is aimed ! at the ISP or other corporate user who wants stability and a ! low change count over the wizzy new features of the latest ! <emphasis>-CURRENT</emphasis> snapshot. Releases can come ! from either branch, but you should only use ! <emphasis>-CURRENT</emphasis> if you are sure that you are ! prepared for its increased volatility (relative to ! <emphasis>-STABLE</emphasis>, that is).</para> ! <para>Releases are only made <link linkend="release-freq">every ! few months</link>. While many people stay more up-to-date with the FreeBSD sources (see the questions on <link linkend="current">FreeBSD-CURRENT</link> and <link linkend="stable">FreeBSD-STABLE</link>) than that, doing so --- 252,267 ---- released in &rel.current.date;. This is also the latest <emphasis>RELEASE</emphasis> version.</para> ! <para>Briefly, <emphasis>-STABLE</emphasis> is aimed at the user ! who wants stability and a minimal number of changes more than ! they want the new (and possibly unstable) features of the ! latest <emphasis>-CURRENT</emphasis> snapshot. Releases can ! come from either branch, but <emphasis>-CURRENT</emphasis> ! should only be used if you are prepared for its increased ! volatility (relative to <emphasis>-STABLE</emphasis>, that is.</para> ! <para>Releases are made <link linkend="release-freq">every few ! months</link>. While many people stay more up-to-date with the FreeBSD sources (see the questions on <link linkend="current">FreeBSD-CURRENT</link> and <link linkend="stable">FreeBSD-STABLE</link>) than that, doing so *************** *** 299,313 **** analyze any problems and only report them if they are deemed to be mistakes rather than <quote>glitches</quote>. Questions such as <quote>make world produces some error about ! groups</quote> on the -CURRENT mailing list are sometimes ! treated with contempt.</para> <para>Every day, <ulink URL="../../../../releases/snapshots.html">snapshot </ulink> releases are made based on the current state of the ! -CURRENT and -STABLE branches. Nowadays, distributions of the ! occasional snapshot are now being made available. The goals ! behind each snapshot release are:</para> <itemizedlist> <listitem> --- 296,310 ---- analyze any problems and only report them if they are deemed to be mistakes rather than <quote>glitches</quote>. Questions such as <quote>make world produces some error about ! groups</quote> on the -CURRENT mailing list may be treated ! with contempt.</para> <para>Every day, <ulink URL="../../../../releases/snapshots.html">snapshot </ulink> releases are made based on the current state of the ! -CURRENT and -STABLE branches. Distributions of the ! occasional snapshot are available. The goals behind each ! snapshot release are:</para> <itemizedlist> <listitem> *************** *** 317,338 **** <listitem> <para>To give people who would like to run -CURRENT or ! -STABLE but who do not have the time and/or bandwidth to follow it on a day-to-day basis an easy way of ! bootstrapping it onto their systems.</para> </listitem> <listitem> ! <para>To preserve a fixed reference point for the code in ! question, just in case we break something really badly ! later. (Although CVS normally prevents anything horrible ! like this happening :)</para> </listitem> <listitem> ! <para>To ensure that any new features in need of testing ! have the greatest possible number of potential ! testers.</para> </listitem> </itemizedlist> --- 314,334 ---- <listitem> <para>To give people who would like to run -CURRENT or ! -STABLE but who do not have the time or bandwidth to follow it on a day-to-day basis an easy way of ! installing it on their systems.</para> </listitem> <listitem> ! <para>To maintain a fixed reference point for the branch in ! question, just in case something gets very badly broken ! later. (Although CVS normally prevents anything this ! horrible from happening :)</para> </listitem> <listitem> ! <para>To ensure that all new features and fixes have the ! greatest possible number of potential testers.</para> </listitem> </itemizedlist> *************** *** 350,357 **** 3-STABLE snapshots are not being produced at the time of this writing (May 2000).</para> ! <para>Snapshots are generated, on the average, once a day for ! all actively developed branches.</para> </answer> </qandaentry> --- 346,353 ---- 3-STABLE snapshots are not being produced at the time of this writing (May 2000).</para> ! <para>Snapshots are usually generated daily for all ! actively developed branches.</para> </answer> </qandaentry> *************** *** 431,453 **** </question> <answer> ! <para>As a general principle, the FreeBSD core team only release ! a new version of FreeBSD when they believe that there are ! sufficient new features and/or bug fixes to justify one, and ! are satisfied that these new developments have been tested ! sufficiently to avoid compromising the stability of the ! release. Release dates are generally announced well in ! advance, so that the people working on the system know ! when their projects need to be finished and tested. ! Many users regard this caution as one of the best ! things about FreeBSD, although ! waiting for all the latest goodies to reach -STABLE ! can be a little frustrating.</para> ! <para>Releases are made about every 4 months on average.</para> <para>For people who need or want a little more excitement, ! binary snapshots are made every day as discussed above.</para> </answer> </qandaentry> --- 427,448 ---- </question> <answer> ! <para>As a rule, the FreeBSD core team only releases a new ! version of FreeBSD when there are a sufficient number of new ! features and bug fixes to justify it, and, more imprtantly, ! when they are satisfied that these changes have been ! thoroughly tested and do not compromise the stability of ! the release. Release dates are generally announced well in ! advance so the developers know when their projects need to ! to be finished and tested. Many users regard this caution ! as one of the best things about FreeBSD, though waiting for ! all the latest goodies to reach -STABLE can be a little ! frustrating.</para> ! <para>Releases are made about every 4 months.</para> <para>For people who need or want a little more excitement, ! binary snapshots are made daily as discussed above.</para> </answer> </qandaentry> *************** *** 501,516 **** <listitem> <para><ulink URL="ftp://releng4.FreeBSD.org/pub/FreeBSD/">4.X ! snapshots</ulink> are usually made once a day.</para> </listitem> <listitem> <para><ulink URL="ftp://current.FreeBSD.org/pub/FreeBSD/"> 5.0 Snapshot</ulink> releases are made once a day for the ! <link linkend="current">-CURRENT</link> branch, these being ! of service purely to bleeding-edge testers and ! developers.</para> </listitem> </itemizedlist> --- 496,510 ---- <listitem> <para><ulink URL="ftp://releng4.FreeBSD.org/pub/FreeBSD/">4.X ! snapshots</ulink> are usually made daily.</para> </listitem> <listitem> <para><ulink URL="ftp://current.FreeBSD.org/pub/FreeBSD/"> 5.0 Snapshot</ulink> releases are made every day for the ! <link linkend="current">-CURRENT</link> branch, these are ! only useful to bleeding-edge testers and developers.</para> </listitem> </itemizedlist> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200202020800.g12805434363>