On Fri, Sep 24, 2004, David M. Fetter wrote:
> On Thu, 2004-09-23 at 23:43, Ralf S. Engelschall wrote:
> > On Fri, Sep 24, 2004, Michael van Elst wrote:
> > Fixed. See http://cvs.openpkg.org/chngview?cn=19174 for details. The
> > fix is now part of OpenPKG-CURRENT's openpkg-tools-0.8.20. Thanks for
> > finding the bug, Michael.
>
> So, I'm curious. Why does this fix go into current and not under the
> UPD directory of release as well? I'm just trying to understand how
> updates are processed and moved around so we can do the best to
> implement things here in our environment that will work with your update
> processes.
Every(!) fix is first applied to CURRENT. Once it is settled and proofed
to be correct (usually by just waiting and not seeing problems or by
obviously correct), it is Merged From CURRENT (MFC) to the latest
RELEASE by merging the changes from CVS's HEAD to the OPENPKG_X_Y_SOLID
branch. From this branch then a package foo-Z-X.Y.N is rolled and placed
into the UPD directory on the FTP server. This whole approach closely
follows the FreeBSD development model and makes sure that we never miss
a fix, i.e. that a next release does not contain a fix which was already
applied to a previous release. Compare this approach for instance to
the one used for developing the Linux kernel (there it occurred already
multiple times that something was already fixed and later releases did
not already contain the fix)...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
