/usr/share/doc/lire/dev-manual/ch19.html is in lire-devel-doc 2:2.1.1-2.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 19. Making a Release</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Lire Developer's Manual"><link rel="up" href="pt04.html" title="Part IV. Lire Developers' Conventions"><link rel="prev" href="ch18s03.html" title="Using the Perl debugger on Lire code"><link rel="next" href="ch19s02.html" title="Tagging the CVS"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 19. Making a Release</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch18s03.html">Prev</a> </td><th width="60%" align="center">Part IV. <span class="application">Lire</span> Developers' Conventions</th><td width="20%" align="right"> <a accesskey="n" href="ch19s02.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 19. Making a Release"><div class="titlepage"><div><div><h2 class="title"><a name="chap:release"></a>Chapter 19. Making a Release</h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch19.html#sect:versionnews">Setting version in NEWS file, checking ChangeLog</a></span></dt><dt><span class="section"><a href="ch19s02.html">Tagging the CVS</a></span></dt><dt><span class="section"><a href="ch19s03.html">Building The Tarball</a></span></dt><dt><span class="section"><a href="ch19s04.html">Building The Debian Package</a></span></dt><dt><span class="section"><a href="ch19s05.html">Building The RPM Package</a></span></dt><dt><span class="section"><a href="ch19s06.html">Making sure the FreeBSD port gets updated</a></span></dt><dt><span class="section"><a href="ch19s07.html">Uploading The Release</a></span></dt><dd><dl><dt><span class="section"><a href="ch19s07.html#id419052">The LogReport Webserver</a></span></dt></dl></dd><dt><span class="section"><a href="ch19s08.html">Advertising The Release</a></span></dt><dd><dl><dt><span class="section"><a href="ch19s08.html#id419178">SourceForge</a></span></dt><dt><span class="section"><a href="ch19s08.html#id419264">Freshmeat.net</a></span></dt></dl></dd></dl></div><p>Before making an official <span class="application">Lire</span> release, it should have
been tested on all supported platforms. A release shouldn't
be made unless <span class="application">Lire</span> builds, installs and generates an ASCII
report from all supported log files on all supported platforms. If
this is not the case, the release should be delayed untill this is
fixed.
</p><p>Making a new release of <span class="application">Lire</span> involves many steps:</p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p>Writing the final version number in NEWS.</p></li><li class="step" title="Step 2"><p>Tagging the CVS tree.</p></li><li class="step" title="Step 3"><p>Building the "Standard" <span class="application">Lire</span> tarball.</p></li><li class="step" title="Step 4"><p>Building the <span class="productname">Debian GNU/Linux</span>™ package.</p></li><li class="step" title="Step 5"><p>Building the RPM package.</p></li><li class="step" title="Step 6"><p>Making sure the FreeBSD package gets updated.</p></li><li class="step" title="Step 7"><p>Uploading the tarballs and making packages available.</p></li><li class="step" title="Step 8"><p>Advertising the release.</p></li></ol></div><div class="section" title="Setting version in NEWS file, checking ChangeLog"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sect:versionnews"></a>Setting version in NEWS file, checking ChangeLog</h2></div></div></div><p>
Inbetween releases, the NEWS file generally reads
"version in cvs". This should of course be changed to e.g.
"version 20011205".
</p><p>
We maintain a ChangeLog file. Make sure the
ChangeLog in the toplevel directory is not too big. If needed,
split off a chunk and move it to doc/. The ChangeLog is
autogenerated from the CVS commits, using the
<span class="command"><strong>cvs2cl</strong></span> tool. One could e.g. run
<strong class="userinput"><code>cvs2cl --prune --stdout -l "-d \>yesterday" -U
../CVSROOT/users</code></strong>. Beware! It might take SourceForge about
a day to make the cvs log available. So you might have to wait a day
between your last commit and running cvs2cl.
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch18s03.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="pt04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch19s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Using the Perl debugger on Lire code </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Tagging the CVS</td></tr></table></div></body></html>
|