On Tue, May 6, 2008 at 9:30 PM, Bob Tarling <[EMAIL PROTECTED]> wrote: > There are deprecated methods in Profile and yet we have not had a > stable release yet with that class. Do we really need to deprecate > under those circumstances.
Although it might be nice to deprecate things for one developer release, if we leave them in too long, we can actually increase the risk that external developers will be caught by surprise when we remove them just before the release. We're close enough to release that it's probably worth taking out anything in this category. As an aside, consistent use of @since annotations would make it easier to tell when things are in this category. I'd recommend we use the stable release version for these so they don't have to be updated e.g. @since 0.26. > Maybe there is a some other last minute tidying up we can do now. > Would it be worth making Profile an interface rather than a class? It would definitely be worth reviewing a major new API like this carefully before release. I went through the other day and restored some methods which had been deprecated, but also coded to unconditionally throw illegal operation exceptions. I didn't have time to go through the entire API. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
