One more question: The scheme depends on actually knowing what
changes have been made to the code. I.e. what is the minimum
version number (major, minor or patch) we must increase?

Ideas?

I know that Cocoon creates a whole new repo for each bump
in minor version number.

We could do something similar - perhaps have a
avalon/framework-4.1 directory and a avalon/framework-4.2 
dir.

/LS

> From: Leo Sutic [mailto:[EMAIL PROTECTED] 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to