camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject [DISCUSS] How to improve the documentation of new functionality (for older releases)
Date Sun, 15 Jan 2012 11:55:39 GMT
At present it's really hard to document new features/improvements which we
back port to older Camel releases. Eg. we have to mention an option is
available in 2.7.5, 2.8.3, 2.9.1 and 2.10.0+ but not in 2.8.0, 2.8.1, 2.8.2
and 2.9.0. This is really puzzling.

Another "issue" I realized today is the Camel manual. For the Camel 2.7.x
branch the actual uploaded manual is 2.7.0. I guess the reason is if we
upload the actual manual we mention also new features which we introduce in
Camel 2.8.x, 2.9.x and 2.10.x which is puzzling. But this means also that
our users cannot find new features/improvements we back ported into the
older branches. More than only annoying...

A few times I read "we will solve this by putting the documentation into
our SCM", if I remember right.
- Do we have concrete plans to solve it?
- What are the plans in detail?
- When do we plan to solve it?

Thanks in advance for your ideas,

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message