Charles Moulliard wrote:
I would like to suggest that the documentation of the web site is updated in
pararrel of making a realese. A tutorial is available for Blueprint but few
info or nothing concerning JNDI (publising and retrieving a OSGI service (or
blueprint service), JPA, Transaction and Web (@Resource, packaging).
Strongly agree. Specifically the blueprint tutorial is out of date
(ARIES-93), the blog sample needs documentation (ARIES-103). I suggest
we raise JIRAs for missing/inadequate docs and gate a release on
resolving them.
Zoe
Kind Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
On Wed, Jan 27, 2010 at 11:37 AM, Valentin Mahrwald <
[email protected]> wrote:
+1 for doing a release.
As for the release version number, would this have any bearing on how we
version our package exports and bundles?
Regards,
Valentin
On 26 Jan 2010, at 17:34, Jeremy Hughes wrote:
There's been a lot of activity lately so I'd like to propose we do a
release so we can get some wider user feedback. I think we should give
it a version of 0.1 and stick to versions <1 while we're in the
Incubator.
Then there is the question of whether to independently version the
high level modules or keep them lock-step. For now I think we should
keep them lock-step until we feel a need to change that.
What does everyone think?
Thanks,
Jeremy
