Could we expose these "provisional" APIs through another
medium? Perhaps a page on the website that lists the "Proposed" features (using
only the "internal" naming convention) and request feedback on those areas for
clients that experiment with using those classes in their products (note I
didn't use the phase "API" here)?
Jim -- would that still be sending the "mixed message"? What's the practice
normally used by other Eclipse teams when experimenting? Do we fall into a
different situation since we have so much functionality and code that has
evolved in a commercial setting which we are now refactoring into tight, open
client API?
-------------------------------------------------------------------------
Kind Regards,
Michael D. Elder
Rational Studio / J2EE Tools
Development
IBM RTP Lab
Ext: (919) 543-8356
T/L: 441-8356
mdelder@xxxxxxxxxx
Tuesday, March 08, 2005 4:07 PM
To: wtp-dev@xxxxxxxxxxx
cc:
From: Arthur Ryman <ryman@xxxxxxxxxx>
Subject: Re: [wtp-dev]
proposed package naming convention to distinguish 'work in progress'
API