I'd suggest copying it and changing the version to 'do-not-use-
SNAPSHOT' or something. Artifacts can be published to the SNAPSHOT
repo but there's no need to formally release as this is really a
development snapshot. It can be patched if something critical comes
up but wouldn't be intended for long term development.
Another alternative is to branch the kernel and do the new work there
merging back in when its complete. I think that might be confusing
though.
--
Jeremy
On Jan 18, 2007, at 8:39 AM, Jim Marino wrote:
On Jan 18, 2007, at 8:27 AM, Rick wrote:
Another question comes to mind, how will we handle issues found in
the "do-not-use" kernel if they are found by extension writers and
are blocking? Do they get fixed ? Parallel development on both
kernels? Blocking till the new kernel is ready?
I'd prefer not to branch. Since this will hopefully be a short
period before we have another release, I think they would block or
a patch could be applied locally to the extension. If someone has
another solution, we could look at that.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
