Brian Moseley wrote:
On 8/27/07, James M Snell <[EMAIL PROTECTED]> wrote:
I haven't really dug into any detail on specific refactorings for the
server module. I like the idea of having some way of allowing an
implementor to provide builder objects to use with a default provider
implementation; I'm just not sure how best to go about it.
definitely the most awkward area of my implementation is how to
serialize my domain model into some format suitable as entry content,
and how to deserialize an incoming entry to apply it to the model,
especially when there are multiple possible representations for a
model object. it would be nice if abdera provided a nice utility for
this, since everybody has to do it.
+1
Regarding the versioning; I'm sure the other committers have their own
thoughts on this, but I had originally considered keeping all incubation
releases as 0.N and only doing a 1.0 release only after we graduate.
Doing so gives us an excuse to keep things fluid and not lock down the
API too prematurely and allows us to get plenty of field experience with
the code to shake out any bugs. N.0 releases always seem so official
and rigid :-). That said, I wouldn't have any strong objections to
putting out a 1.0 in the not too distant future.
i wouldn't expect a 1.0 to be released until after graduating, but i'm
not sure there are any hard and fast rules.
Incubation doesn't really imply anything about APIs, stability or
releases (other than that they need to go through more legal scrutiny).
Its also good to keep in mind that a solid 1.0 release can help pull a
project out of incubation. In CXF we got a lot more involvement once we
got a .0 release out. While we haven't left yet, I view it as a
critical step along the way.
- Dan
--
Dan Diephouse
MuleSource
http://mulesource.com | http://netzooid.com/blog
|
