The 0.18.0 release and Repository Rules

	Well, it looks like the different sub-projects of the 0.18.0 release 
are coming to a close. If everyone working on a sub-project could email 
me where things stand I'll make a decision as to whether to declare a 
freeze wednesday night and start tagging and building betas. If all 
goes well we should be able to start putting out betas by thursday or 
friday.

	Its come to my attention that the repository hasn't been in the best 
of shape in the last few days. This is probably my fault :) . But 
regardless, it seems that its about time to start putting some process 
around CVS commits. Starting now :

	1) Send me patches / diffs of all proposed changes and get my 
approval. There are a number of cooks in this pot right now and I need 
to make sure I know what's going in :)
	
	2) Make sure that everything builds on your local machine (after a 
distclean all the way through to make install) before you commit. If 
you have a workarea on webcodex, you might try to test compile your 
changes there as well. Webcodex uses gcc 2.96, an older version that 
isn't as ... forgiving :) about certain things.

	3) Make sure that all tests in the tests folder that pass before you 
make your changes still pass after you make your changes.

	4) Verify that mod_moto, mmc based module compilation, and mxc based 
extension compilation still work if there is even the slightest chance 
your change has impacted these areas.

	Please make the effort to do the above before you commit :)

	-Dave