On Mar 28, 2006, at 1:08 PM, Allen Gilliland wrote:
David M Johnson wrote:
eeks, now we are working backwards. if these things are still
"experimental features" and need to be kept low profile then i am
-1 for moving them out of the sandbox.
also, after "Admin protocol has had sufficient review"? that
review needs to happen before we move it out of the sandbox and
package the code into a release.
If we're going to get help with interop testing, which is very
important for these protocols, it would be *really* helpful to have
these features built-in but disabled by default.
i am okay with commiting them to the core code if the
implementation is complete but may have some changes in the future,
but we still need to treat them as if these are fully working and
fully functional features. if we don't believe that is true then
we can't release them.
now that i think about it, maybe it is not a good idea to squeeze
this in at such a late time in the release process.
I see that last point, but these changes are isolated to two
Servlets, don't impact any existing features and are disabled by
default.
It would be helpful and much more convenient for me and other folks
working on this stuff to avoid the custom build setup. I really don't
think there is a downside here.
- Dave
