Re: [CryptoAPI-devel] testing...

[Kyle M. <ky...@de...>]

(sorry forgot to send this to the mailing list)

On Mon, Feb 25, 2002 at 01:02:11AM +0100, Herbert Valerio Riedel wrote:
> 1. how to automate the task of creating a kernel patch from the
> cryptoapi-CVS? or maybe just do it like the frees/wan people do?
> 2. how to handle jari's and my loop-IV fix approach in a compatible way.
> 3. documentation update
> 4. some stuff I forgot... :-/
> 

This one should be easy, do all development in a HEAD branch, and when a
new kernel is released, create a branch for it, and stabilize the
branch, while all main work continues on HEAD.

Only problem with this approach is releases for old kernels stagnates,
so sticking to the stable tree, where people are nearly guaranteed to
upgrade, is okay.

I'll suck down the cvs tree in a few minutes. Seeing how long it is
taking for 2.4.18, I think shooting for a stable version for it would be
a good idea, since at this rate it will be current for ages.

I suppose coordination with the FreeS/WAN people would be a good idea,
especially if they began using the CryptoAPI ciphers.

I'll being by looking into the documentation, that should be a good way
of getting my feet wet.

regards,
	kyle
-- 
copyleft (c) 2002, Kyle McMartin