Who's has the administrative power to make such changes?
It's easy enough for self-contained things like javadoc, but other
areas might have layered requirements.
I suppose we need to define how it should be done also.
On Sep 24, 2007, at 2:33 PM, Eduardo Pelegri-Llopart wrote:
> +1
>
> Bill Shannon wrote:
>> Lloyd L Chambers wrote:
>>> I'm thinking that the entire javadoc tree for AMX (and anything
>>> else that is an API on glassfish.dev.java.net) should be forked
>>> each time we release, so that one can go to the Javadoc for V1,
>>> V2, V3, etc. Otherwise, as GlassFish is revised, the current
>>> javadoc will overwrite the javadoc for earlier versions.
>>>
>>> Thoughts?
>> I agree.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>