head	1.16;
access;
symbols;
locks; strict;
comment	@# @;


1.16
date	2006.01.19.21.35.02;	author openpkg;	state Exp;
branches;
next	1.15;
commitid	Qam512JcrAhLVfir;

1.15
date	2005.02.24.15.55.52;	author rse;	state Exp;
branches;
next	1.14;

1.14
date	2005.01.18.09.11.24;	author thl;	state Exp;
branches;
next	1.13;

1.13
date	2004.10.20.08.18.17;	author rse;	state Exp;
branches;
next	1.12;

1.12
date	2004.02.27.15.10.13;	author thl;	state Exp;
branches;
next	1.11;

1.11
date	2004.02.25.09.26.00;	author thl;	state Exp;
branches;
next	1.10;

1.10
date	2003.08.07.14.46.09;	author thl;	state Exp;
branches;
next	1.9;

1.9
date	2003.04.17.07.26.26;	author rse;	state Exp;
branches;
next	1.8;

1.8
date	2003.03.15.16.16.21;	author rse;	state Exp;
branches;
next	1.7;

1.7
date	2003.01.22.13.12.54;	author rse;	state Exp;
branches;
next	1.6;

1.6
date	2003.01.19.11.44.00;	author rse;	state Exp;
branches;
next	1.5;

1.5
date	2003.01.01.14.47.58;	author rse;	state Exp;
branches;
next	1.4;

1.4
date	2002.12.26.14.34.13;	author rse;	state Exp;
branches;
next	1.3;

1.3
date	2002.12.19.10.52.43;	author rse;	state Exp;
branches;
next	1.2;

1.2
date	2001.11.30.23.12.31;	author rse;	state Exp;
branches;
next	1.1;

1.1
date	2001.11.30.16.04.22;	author rse;	state Exp;
branches;
next	;


desc
@@


1.16
log
@point out releases obey default options only
@
text
@
#use "page.inc" page=releng

<title>OpenPKG Release Engineering</title>

<h1>OpenPKG Release Engineering</h1>

<h2>Package Classification</h2>

OpenPKG packages are grouped into multiple classes.
The class of a source package can be determined by running:

<pre>
$ openpkg rpm -qp --qf '%{CLASS}' <i>foo-1.42-2.3.0.src.rpm</i>
</pre>

The class of an installed package can be determined by running:

<pre>
$ openpkg rpm -q --qf '%{CLASS}' <i>foo</i>
</pre>

The classes are differentiated by multiple attributes as
described by the following table:

<p>
<define-tag yes>
<td align=center><img src="status.img/icon-ok.gif" alt="yes"></td>
</define-tag>
<define-tag no>
#<td align=center><img src="status.img/icon-x.gif" alt="yes"></td>
<td align=center>&nbsp;</td>
</define-tag>
<define-tag ab>
<td align=center>%0</td>
</define-tag>

<table cellspacing=0 cellpadding=1 border=0 bgcolor="#a5a095"><tr><td>
<table cellspacing=1 cellpadding=1 border=0 bgcolor="#e5e0d5">
  <tr><td> </td>                      <ab RTT> <ab SAP> <ab FPS> <ab RSS> <ab RBP> <ab RSP> <ab BLD> <ab PKG> </tr>
  <tr bgcolor="#f5f0e5"><td>CORE</td> <yes>    <yes>    <yes>    <yes>    <yes>    <yes>    <yes>    <yes>    </tr>
  <tr bgcolor="#d5d0c5"><td>BASE</td> <no>     <yes>    <yes>    <yes>    <yes>    <yes>    <yes>    <yes>    </tr>
  <tr bgcolor="#f5f0e5"><td>PLUS</td> <no>     <no>     <no>     <no>     <no>     <yes>    <yes>    <yes>    </tr>
  <tr bgcolor="#f5f0e5"><td>EVAL</td> <no>     <no>     <no>     <no>     <no>     <no>     <no>     <yes>    </tr>
  <tr bgcolor="#d5d0c5"><td>JUNK</td> <no>     <no>     <no>     <no>     <no>     <no>     <no>     <no>     </tr>
</table>
</td></tr></table>

<p>
<table cellspacing=0 cellpadding=0>
  <tr>
    <td colspan=2>Legend:</td>
  </tr>
  <tr><td>RTT:&nbsp;</td><td>Run-Time Tested</td></tr>
  <tr><td>SAP:&nbsp;</td><td>Security Advisories and Patches</td></tr>
  <tr><td>FPS:&nbsp;</td><td>Full Platform Support Build Requirement</td></tr>
  <tr><td>RSS:&nbsp;</td><td>Release Show-Stopper</td></tr>
  <tr><td>RBP:&nbsp;</td><td>Release Binary Package</td></tr>
  <tr><td>RSP:&nbsp;</td><td>Release Source Package</td></tr>
  <tr><td>BLD:&nbsp;</td><td>Building Successful on all Supported Platforms</td></tr>
  <tr><td>PKG:&nbsp;</td><td>Packaging Completed</td></tr>
</table>
Notice: releases obey default options only!

<h2>Version Numbering Scheme</h2>

OpenPKG packages are available in various versions, derived from different
source branches. These directly map to the internal structure of the <a
href="http://www.openpkg.org/cvsweb/cvsweb.cgi/">CVS repository</a> module <a
href="http://www.openpkg.org/cvsweb/cvsweb.cgi/openpkg-src/"><tt>openpkg-src</tt></a>.
This CVS structure is summarized in the following figure.

<p>
<a href="cvs.png"><img src="cvs.gif" border=0 alt=""></a>
<center>
<b>Figure:</b> OpenPKG CVS Repository
(large: <a href="cvs.png">PNG</a>, <a href="cvs.ps">PS</a>)
</center>

<p>
As one can see, there are three types of branches in the OpenPKG CVS
repository. The trunk (<tt>HEAD</tt>) where all development efforts are placed
and which holds "OpenPKG -CURRENT"; the "OpenPKG -STABLE" branches
(<tt>OPENPKG_N_STABLE</tt>) which hold the stable releases; and the "OpenPKG
-SOLID" sub-branches (<tt>OPENPKG_N_M_SOLID</tt>) which hold the updates for
stable releases. This release engineering approach resembles the one the <a
href="http://www.freebsd.org/">FreeBSD</a> project successfully follows since
years.

<p>
Our developer's <a href="cvs.txt">summary table</a> shows the details how CVS
tag/branch names and community/marketing names are related and where the
corresponding distribution packages are located.

<p>
The <a href="http://bf.openpkg.org/bfui.cgi">BuildFarm</a> activities can be viewed online.

<p>
See also:
<ul class="compact">
<li><a href="http://www.freebsd.org/internal/releng.html">
    FreeBSD Release Engineering Process</a>
<li><a href="http://people.freebsd.org/~jhb/docs/releng.txt">
    John Baldwin's Release Engineering Proposal</a>
<li><a href="http://www.netbsd.org/developers/releng/release-process.html">
    NetBSD Release Engineering Process</a>
</ul>

<h2>Third-Party Hints</h2>

For developing new packages, you can sometimes get hints by looking
at the packaging efforts of other projects. You can find them at the
following locations:

<p>
<ul class="compact">
<li><a href="http://www.freebsd.org/ports/index.html">FreeBSD Ports</a>
<li><a href="http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/">NetBSD pkgsrc</a>
<li><a href="http://packages.qa.debian.org/">Debian GNU/Linux, Packaging Tracking System</a>
<li><a href="http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/SPECS/vim/">Mandrake Linux, CVS of RPM .specs</a>
<li><a href="ftp://ftp.redhat.com/pub/redhat/linux/rawhide/SRPMS/SRPMS/">RedHat Linux, Source RPMs of Rawhide</a>
<li><a href="ftp://ftp.suse.com/pub/unitedlinux/1.0/src/">UnitedLinux, Source RPMs of UnitedLinux 1.0</a>
<li><a href="ftp://ftp.suse.com/pub/suse/i386/8.1/suse/src/">SuSE Linux, Source RPMs of SuSE 8.1</a>
<li><a href="ftp://ftp.conectiva.com/pub/conectiva/snapshot/">Connectiva Linux, Source RPMs of Snapshot</a>
<li><a href="http://cvs.pld.org.pl/SPECS/">PLD Linux, CVS of RPM .specs</a>
<li><a href="ftp://ftp.slackware.com/pub/slackware/slackware-current/source/">Slackware Linux, Current Sources</a>
<li><a href="ftp://ftp.turbolinux.com/pub/TurboLinux/TurboLinux/ia32/Server/8/source/SRPMS/">TurboLinux, Source RPMs</a>
<li><a href="ftp://ftp.sco.com/pub/OpenLinux3.1.1/Server/SRPMS/">SCO OpenLinux, Source RPMs</a>
<li><a href="http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-x86/">Gentoo Linux, CVS of packaging sources</a>
<li><a href="http://cvs.linuxfromscratch.org/index.cgi/hints/">Linux From Scratch, CVS of packaging hints</a>

</ul>

@


1.15
log
@update website for OpenPKG 2.3 release
@
text
@d63 1
@


1.14
log
@dismantle old build farm status viewing from OpenPKG web server and provide direct links to master
@
text
@d14 1
a14 1
$ openpkg rpm -qp --qf '%{CLASS}' <i>foo-1.42-2.2.0.src.rpm</i>
@


1.13
log
@one more lifting to 2.2
@
text
@d95 1
a95 1
The latest package building status can be found <a href="status.cgi">here</a>.
@


1.12
log
@cosmetics
@
text
@d14 1
a14 1
$ openpkg rpm -qp --qf '%{CLASS}' <i>foo-1.42-2.0.0.src.rpm</i>
@


1.11
log
@flush pending updates for OpenPKG 2.0
@
text
@d99 1
a99 1
<ul>
d115 1
a115 1
<ul>
@


1.10
log
@spell checking and correcting
@
text
@d14 1
a14 1
$ rpm -qp --qf '%{DISTRIBUTION}' <i>foo-1.2-3.4.src.rpm</i>
d20 1
a20 1
$ rpm -q --qf '%{DISTRIBUTION}' <i>foo</i>
d40 1
a40 1
  <tr><td> </td>                      <ab RTT> <ab SAP> <ab OPS> <ab RSS> <ab RBP> <ab RSP> <ab BLD> <ab PKG> </tr>
d56 1
a56 1
  <tr><td>OPS:&nbsp;</td><td>Official Platform Support Build Requirement</td></tr>
d58 1
a59 1
  <tr><td>RBP:&nbsp;</td><td>Release Binary Package</td></tr>
@


1.9
log
@remember PLD CVS stuff
@
text
@d23 1
a23 1
The classes are differenciated by multiple attributes as
@


1.8
log
@remember LFS
@
text
@d124 1
@


1.7
log
@flush everything prepared for OpenPKG 1.2
@
text
@d128 1
@


1.6
log
@cleanup and enhance class table
@
text
@d125 4
@


1.5
log
@remember URLs to other vendor packaging efforts
@
text
@a37 4
<table>
<tr>
<td align=top>

d40 6
a45 7
  <tr><td> </td>    <ab RTT> <ab SAP> <ab RSS> <ab REL> <ab BLD> <ab PKG> <ab PUB> </tr>
  <tr bgcolor="#f5f0e5"><td>CORE</td> <yes>    <yes>    <yes>    <yes>    <yes>    <yes>    <yes>    </tr>
  <tr bgcolor="#d5d0c5"><td>BASE</td> <no>     <yes>    <yes>    <yes>    <yes>    <yes>    <yes>    </tr>
  <tr bgcolor="#f5f0e5"><td>PLUS</td> <no>     <no>     <no>     <yes>    <yes>    <yes>    <yes>    </tr>
  <tr bgcolor="#d5d0c5"><td>PRIV</td> <no>     <no>     <no>     <no>     <yes>    <yes>    <no>     </tr>
  <tr bgcolor="#f5f0e5"><td>EVAL</td> <no>     <no>     <no>     <no>     <no>     <yes>    <yes>    </tr>
  <tr bgcolor="#d5d0c5"><td>JUNK</td> <no>     <no>     <no>     <no>     <no>     <no>     <yes>    </tr>
d49 1
a49 8
</td>
<td>
&nbsp;
&nbsp;
&nbsp;
</td>
<td align=top>

d56 1
d58 3
a60 2
  <tr><td>REL:&nbsp;</td><td>Release Package</td></tr>
  <tr><td>BLD:&nbsp;</td><td>Building Successful</td></tr>
a61 5
  <tr><td>PUB:&nbsp;</td><td>Publically Distributed</td></tr>
</table>

</td>
</tr>
@


1.4
log
@PRIV packages have to build; EVAL packages have to be packaged, but must not build everywhere
@
text
@d123 19
@


1.3
log
@commit pending changes to CVS
@
text
@d31 1
d48 2
a49 2
  <tr bgcolor="#d5d0c5"><td>PRIV</td> <no>     <no>     <no>     <no>     <no>     <yes>    <no>     </tr>
  <tr bgcolor="#f5f0e5"><td>EVAL</td> <no>     <no>     <no>     <no>     <no>     <no>     <yes>    </tr>
@


1.2
log
@add pointers
@
text
@d8 72
d107 3
@


1.1
log
@Add release engineering page.
@
text
@d36 11
@