Release WcfFacility?

[Craig Neuwirt]

Hey all,

  I know the release of the WCF Facility has been way behind.  The source has been stable for a while, but as you know docs are not there.  There are really endless scenarios to talk about so I could really use your help.  If you have used the facility and care to contribute to the docs, Krzystof has added a placeholder for WCF Facility on our new wiki.

In the meantime, do you want me to release the WCF Facility in the absence of good docs, or wait?

craig

--
You received this message because you are subscribed to the Google Groups "Castle Project Users" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.

[Bailey Ling]

IMO, I think the facility should be released when the merged Castle.Core and Castle.Windsor are released (otherwise people will have another round of reference updates again).  I think this should happen sooner than later because Krzysztof added too much awesome to trunk (or ehh..master) lately.

[Krzysztof Koźmic]

Frankly, I think the facility is the least trivial of all facilities we have an we really need solid documentation in place in order to call it released, as opposed to just published.

There's value in having the release now, but I think we should have at least docs for the basic scenarios to at least point people in the right direction and give them the sense of what the facility can do.

I started adding documentation for asynchronous calls already. If anyone who ever used the facility has a moment to contribute at least few paragraphs or code snippets it would help us push matters forward.

And regardless of whether we (you, the users) decide we should push the release now, I'd really like to have more or less complete docs in place for next release of Windsor (v2.5) which I plan to release in beta within a month, and RTW one month after that.

K