[1755] in NetBSD-Development
Operation of source-sipb
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Sep 1 11:58:09 1998
To: sipb-athena@MIT.EDU
Date: Tue, 01 Sep 1998 11:57:45 EDT
From: Greg Hudson <ghudson@MIT.EDU>
I'd like to alert or remind linux-dev of a few things:
* source-sipb tracks the Athena mainline. There are already
post-8.2 changes on the Athena mainline (and in source-sipb)
which are not necessarily well-tested. As far as I know,
linux-dev has been dealing with the mainline and not with a
release branch at this point. This is only mildly tenable
for now, and will certainly become less tenable when more
destabilizing changes hit the Athena mainline and are
imported into source-sipb.
* source-sipb has a release branch called source-sipb-8_2,
which was used to build the recent NetBSD-Athena release.
Unfortunately, the bulk of Aaron's work was committed after
that branch was made, but the number of changes he's
committed so far is manageable.
Either linux-dev can share the release branch or it can have
a separate release branch. Either way, people doing work on
the release should have the necessary clue about CVS and the
operation of source-sipb to know how to properly make patch
releases--without making life difficult for the other port
if the release branch is shared.
* source-sipb has a review procedure. Nothing should just get
committed without first going through sipb-source-reviewers.
Please see /mit/source-sipb/doc/sipb.
* The dev cell has a space commitment to the SIPB Athena
ports. Things like the build volume for Linux, or a
checkout of some hypothetical source-sipb-8.2linux tree, can
come from the dev cell.
