Hi,
With all these compile problems (also with the latest version) maybe there
should be some kind of release engineering process to make each release as
problem free as possible. Something like this:
#0 Darren/someone thinks it release time. set x=something, y=somethig, z=1
#1 cvs tag IPF-4_x_z_RCz and create tarball
#2 ask the users on the mailing list to test it for max W weeks (maybe W=1)
#3 if problems detected then { z++; goto #1 }
#4 tag the final release
I'd also like to see the above implemented when speaking as the NetBSD IPF
maintainer. I'd like to shake nost of the problems before importing new release
into NetBSD. In other words, I'd like to make things easier for me :-)
Martti
