On Feb 22, 2007, at 6:47 AM, Rick Rineholt wrote:
Jim Marino wrote:
On Feb 22, 2007, at 4:40 AM, Rick Rineholt wrote:
I didn't see any mention what bindings are supported or have been
tested with this kernel release. In past we had several web
services, RMI all validating that the kernel and the SPIs. We
also had several implementation supported Java script, Ruby. It
was my experience that these really fleshed out a lot of issues
and gave a lot of confidences the kernel was working and could be
used to build upon by people wanted to build extensions.
That's one of the goals of having the kernel release, to get
feedback and validation on the SPI :-) Also, one of the goals of
modularity as I understand it was to enable releases early and
often, with kernel coming out before extensions. Otherwise, we
will wind up in the unworkable situation we did with the past two
milestones releases.
In any event, the SPI for bindings has not significantly changed
from M2. I suspect they will somewhat when we introduce full
support for federation, put IMO it is important we get something
out now to validate where we are.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
If I start taking this kernel release and find issues what will be
the plan of action? Wait for the next release ? Goto the next
SNAPSHOT published driver?
It depends on if the release has gone out. If not, then we need to
consider if the fix is small enough to incorporate or should be
pushed out to the next release. Assuming the release has gone out,
there are two options, which are not exclusive: move to SNAPSHOT (not
the 'next' snapshot as SNAPSHOT continually changes) or publish a new
release. Now that we are trying to release early, release often,
releases can be done at a very quick pace. Those of us working in
trunk would like to avoid months-long release processes and hence our
desire to start getting these releases out.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
