On 27/02/2009, Stefan Bodewig <bode...@apache.org> wrote: > On 2009-02-27, Christian Grobmeier <grobme...@gmail.com> wrote: > > >>> My status: I started with implementing on that this morning and > >>> figured out that its not a very easy task. Even when I have it > >>> finished in a good time, there should be a good amount of testing > >>> imho. > > >> we could label that part of the API unstable/experimental - or leave > >> it out of the release completely. > > > Depends on when the release is scheduled. If we start the release > > process next week or so, I would say leave it out completly. > > > Next week may be a bit too ambitious, we'd have to move out of the > sandbox, which takes a vote and cut a release which takes another > vote. > > In parallel to "graduation" we may be able to finish the stuff we want > to see done before the 1.0 release. >
I'd like to see some statements in the Javadoc about the intended thread safety or otherwise of the classes. I expect some classes are not thread-safe - e.g. streams - but there may be some utility classes that are thread-safe. It would be useful to document this both for the user and developer. However, if there are any classes that are thread-hostile (*), (I've not noticed any) I would expect these to be fixed before release! (*) e.g. mutable static variable > > Stefan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
