The Committers for each Jakarta Apache and XML Apache project would
decide when an API is deprecated, and what notice to give where -- just
as the Taglibs Committers would decide when the API for a tag changes.
The best advice would be that if your project is dependent on another
API, someone should be watching the DEV list. But, if you miss
something, GUMP is there to catch it before things go too far;-)
Though, perhaps we should encourage subprojects to announce API
deprecations on the Committers list, especially when they know other
Jakarta products depend on them.
But, are the Jarkara and XML Committers lists separate? If so, should
they be?
Glenn Nielsen wrote:
> Who decides that an API is deprecated and no longer supported?
>
> Can other projects comment on these decisions before it is made?
> (For examples James comments about providing backward compatability)
>
> Where are notifications about this sent?
>
> How much advance notice is given so that projects which have dependencies
> can take care of it before you enforce it with GUMP?
>
> Perhaps GUMP could be run once when a decision to deprecate an API
> has been made so that those projects who are using the old API can
> be identified and notified. (So that we don't get a long build failure
> email every single day on the list)
>
> Then later after a grace period, the nightly GUMP starts enforcing it.
>
> Is there any place where the minimum API dependencies are documented
> so that developers can determine in advance if they will be in
> compliance?
>
> Regards,
>
> Glenn
