Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7E5CF.85BBC93F"
Subject: Futurific Documentation
Date: Thu, 23 Aug 2007 17:49:46 -0400
Message-ID: <D1AE8A943CFBEE408A89F87397B024D402285FB9@tewk-mbpf2>
Thread-Topic: Futurific Documentation
Thread-Index: Acflz4XUWKM8P4hHTOKwKhV9ahWI0Q==
From: "Christopher Moesel" <Christopher_Moesel@avid.com>
To: <cxf-dev@incubator.apache.org>

------_=_NextPart_001_01C7E5CF.85BBC93F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hey CXF Team,

=20

This is just a warning about documentation.  Wikis are totally cool, and
it's awesome that we can update docs on the fly, but please beware when
documenting as-of-yet unreleased features. =20

=20

I just spent some time trying to figure out why my policy attachments
aren't working-only to eventually realize that the online docs
represented what was in trunk, not what was in 2.0.1.  I had to dig into
the history of the page to see how to do it with the code that is
currently the latest release.  (BTW-the new policy config stuff looks
pretty cool...)

=20

Anyway, it would be really helpful if we could clearly indicate in the
docs when they reflect unreleased capabilities (and don't remove the old
docs until the new release).

=20

Thanks (and keep up the great work!  I hope to be contributing more
myself soon!)

Chris

=20

=20


------_=_NextPart_001_01C7E5CF.85BBC93F--