christian.heinrich at owasp.org
Wed Mar 9 20:31:09 EST 2011
On Thu, Mar 10, 2011 at 10:31 AM, Chris Schmidt <chris.schmidt at owasp.org> wrote:
> This is very risky to remove before the 2.0 GA Release. Can we just
> deprecate it for GA and remove it in a subsequent version?
I have no issue with the how the ESAPI Project Leader(s) determines
the easiest path (e.g. in the next major release) to separate Java WAF
from Java ESAPI 2.0 GA?
Should this be documented in the Java ESAPI Roadmap so that the end
users are aware of this?
More information about the Esapi-user