Sophie: howto-html-en-20080722-2mdv2010.1 noarch

howto-html-en-20080722-2mdv2010.1.noarch.rpm

<HTML
><HEAD
><TITLE
>Software Release Practice HOWTO</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.63
"><LINK
REL="NEXT"
TITLE="Introduction"
HREF="introduction.html"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="AEN2"
>Software Release Practice HOWTO</A
></H1
><H3
CLASS="AUTHOR"
><A
NAME="AEN4"
>Eric Steven Raymond</A
></H3
><DIV
CLASS="AFFILIATION"
><SPAN
CLASS="ORGNAME"
><A
HREF="http://www.tuxedo.org/~esr/"
TARGET="_top"
>    Thyrsus Enterprises</A
><BR></SPAN
><DIV
CLASS="ADDRESS"
><P
CLASS="ADDRESS"
>&nbsp;&nbsp;&nbsp;&nbsp;esr@thyrsus.com<br>
&nbsp;&nbsp;&nbsp;&nbsp;</P
></DIV
></DIV
><P
CLASS="COPYRIGHT"
>Copyright &copy; 2000 by Eric S. Raymond</P
><DIV
CLASS="REVHISTORY"
><TABLE
WIDTH="100%"
BORDER="0"
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
COLSPAN="3"
><B
>Revision History</B
></TH
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 3.4</TD
><TD
ALIGN="LEFT"
>2002-01-04</TD
><TD
ALIGN="LEFT"
>Revised by: esr</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>More about good patching practice.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 3.3</TD
><TD
ALIGN="LEFT"
>2001-08-16</TD
><TD
ALIGN="LEFT"
>Revised by: esr</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>New section about how to send good patches.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 3.2</TD
><TD
ALIGN="LEFT"
>2001-07-11</TD
><TD
ALIGN="LEFT"
>Revised by: esr</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>Note about not relying on proprietary components.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 3.1</TD
><TD
ALIGN="LEFT"
>2001-02-22</TD
><TD
ALIGN="LEFT"
>Revised by: esr</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>LDP Styleguide fixes.</TD
></TR
><TR
><TD
ALIGN="LEFT"
>Revision 3.0</TD
><TD
ALIGN="LEFT"
>2000-08-12</TD
><TD
ALIGN="LEFT"
>Revised by: esr</TD
></TR
><TR
><TD
ALIGN="LEFT"
COLSPAN="3"
>First DocBook version.  Advice on SourceForge and a major section
	 on documentation practice added.</TD
></TR
></TABLE
></DIV
><DIV
><DIV
CLASS="ABSTRACT"
><A
NAME="AEN42"
></A
><P
></P
><P
>This HOWTO describes good release practices for Linux and other
open-source projects.  By following these practices, you will make it
as easy as possible for users to build your code and use it, and for
other developers to understand your code and cooperate with you to
improve it.</P
><P
>This document is a must-read for novice developers.  Experienced
developers should review it when they are about to release a new
project.  It will be revised periodically to reflect the evolution of
good-practice standards.</P
><P
></P
></DIV
></DIV
><HR></DIV
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>1. <A
HREF="introduction.html"
>Introduction</A
></DT
><DD
><DL
><DT
>1.1. <A
HREF="introduction.html#PURPOSE"
>Why this document?</A
></DT
><DT
>1.2. <A
HREF="introduction.html#NEWVERSIONS"
>New versions of this document</A
></DT
></DL
></DD
><DT
>2. <A
HREF="patching.html"
>Good patching practice</A
></DT
><DD
><DL
><DT
>2.1. <A
HREF="patching.html#AEN65"
>Do send patches, don't send whole archives or files</A
></DT
><DT
>2.2. <A
HREF="patching.html#AEN75"
>Send patches against the current version of the code.</A
></DT
><DT
>2.3. <A
HREF="patching.html#AEN80"
>Don't include patches for generated files.</A
></DT
><DT
>2.4. <A
HREF="patching.html#AEN89"
>Don't send patch bands that just tweak RCS or SCCS $-symbols.</A
></DT
><DT
>2.5. <A
HREF="patching.html#AEN96"
>Do use -c or -u format, don't use the default (-e) format</A
></DT
><DT
>2.6. <A
HREF="patching.html#AEN103"
>Do include documentation with your patch</A
></DT
><DT
>2.7. <A
HREF="patching.html#AEN110"
>Do include an explanation with your patch</A
></DT
><DT
>2.8. <A
HREF="patching.html#AEN125"
>Do include useful comments in your code</A
></DT
></DL
></DD
><DT
>3. <A
HREF="naming.html"
>Good project- and archive- naming practice</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="naming.html#AEN142"
>Use GNU-style names with a stem and major.minor.patch numbering.</A
></DT
><DT
>3.2. <A
HREF="naming.html#LOCAL"
>But respect local conventions where appropriate</A
></DT
><DT
>3.3. <A
HREF="naming.html#PREFIX"
>Try hard to choose a name prefix that is unique and easy to type</A
></DT
></DL
></DD
><DT
>4. <A
HREF="licensetheory.html"
>Good licensing and copyright practice: the theory</A
></DT
><DD
><DL
><DT
>4.1. <A
HREF="licensetheory.html#COPYRIGHTS"
>Open source and copyrights</A
></DT
><DT
>4.2. <A
HREF="licensetheory.html#OPENSOURCE"
>What qualifies as open source</A
></DT
></DL
></DD
><DT
>5. <A
HREF="licensepractice.html"
>Good licensing and copyright practice: the practice</A
></DT
><DD
><DL
><DT
>5.1. <A
HREF="licensepractice.html#HOLDER"
>Make yourself or the FSF the copyright holder</A
></DT
><DT
>5.2. <A
HREF="licensepractice.html#OSD"
>Use a license conformant to the Open Source Definition</A
></DT
><DT
>5.3. <A
HREF="licensepractice.html#UNORIGINAL"
>Don't write your own license if you can possibly avoid it.</A
></DT
></DL
></DD
><DT
>6. <A
HREF="develpractice.html"
>Good development practice</A
></DT
><DD
><DL
><DT
>6.1. <A
HREF="develpractice.html#LANGUAGE"
>Write either pure ANSI C or a portable scripting language</A
></DT
><DT
>6.2. <A
HREF="develpractice.html#PROPRIETARY"
>Don't rely on proprietary code</A
></DT
><DT
>6.3. <A
HREF="develpractice.html#CPORT"
>Follow good C portability practices</A
></DT
><DT
>6.4. <A
HREF="develpractice.html#AUTOCONF"
>Use autoconf/automake/autoheader</A
></DT
><DT
>6.5. <A
HREF="develpractice.html#SANITYCODE"
>Sanity-check your code before release</A
></DT
><DT
>6.6. <A
HREF="develpractice.html#SANITYDOCS"
>Sanity-check your documentation and READMEs before release</A
></DT
></DL
></DD
><DT
>7. <A
HREF="distpractice.html"
>Good distribution-making practice</A
></DT
><DD
><DL
><DT
>7.1. <A
HREF="distpractice.html#TARBALLS"
>Make sure tarballs always unpack into a single new directory</A
></DT
><DT
>7.2. <A
HREF="distpractice.html#README"
>Have a README</A
></DT
><DT
>7.3. <A
HREF="distpractice.html#FILENAMES"
>Respect and follow standard file naming practices</A
></DT
><DT
>7.4. <A
HREF="distpractice.html#UPGRADEABILITY"
>Design for Upgradability</A
></DT
><DT
>7.5. <A
HREF="distpractice.html#RPMS"
>Provide RPMs</A
></DT
></DL
></DD
><DT
>8. <A
HREF="documentation.html"
>Good documentation practice</A
></DT
><DD
><DL
><DT
>8.1. <A
HREF="documentation.html#DOCPRACTICE"
>Good practice in the present</A
></DT
><DT
>8.2. <A
HREF="documentation.html#AEN449"
>Good practice for the future</A
></DT
></DL
></DD
><DT
>9. <A
HREF="communication.html"
>Good communication practice</A
></DT
><DD
><DL
><DT
>9.1. <A
HREF="communication.html#ANNOUNCE"
>Announce to c.o.l.a and Freshmeat</A
></DT
><DT
>9.2. <A
HREF="communication.html#NEWSGROUP"
>Announce to a relevant topic newsgroup</A
></DT
><DT
>9.3. <A
HREF="communication.html#WEBSITE"
>Have a website</A
></DT
><DT
>9.4. <A
HREF="communication.html#LISTS"
>Host project mailing lists</A
></DT
><DT
>9.5. <A
HREF="communication.html#ARCHIVES"
>Release to major archives</A
></DT
></DL
></DD
><DT
>10. <A
HREF="management.html"
>Good project-management practice</A
></DT
></DL
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="introduction.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Introduction</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>