On Mon, 16 Apr 2001, Mike Campbell wrote:
> > Is it important to copy all this stuff into Sandbox for
> > evaluation, or can we just have a proposal that says "go look at the
> > following classes in the foo project"?
>
> Doing that would assume that the foo project continues to use that to which
> you are referring. If that changes, you'd have to migrate it to the sandbox
> then, or switch with it.
>
> Being as this is the 'commons' project, would it not make sense to reverse
> the whole thing, have the things "live" here and have "foo" reference it
> here? Or am I misunderstanding what the sandbox is for?
>
My plan (at least for Struts), and assuming Digester is approved as a
Commons package, is as follows:
* For Struts 1.0 (final release before JavaOne), deprecate the
corresponding code inside Struts, but continue to use it.
* For Struts 1.1, switch to dependence on the "jakarta-commons" version
and remove the "inside" code.
I do not personally plan to ever create an external dependency on a
sandbox pacakge (because the rules for sandbox say you never have to do a
"release"). Others may have different ideas.
Craig
