Is this wise to call the package name indevelopment? I would not want the job of refactoring the code when its production ready, or is it never going to be used outside the package until its ready?
As you sent a message to the list explaining for contents of the package not to be used until completed, is it really necessary to give it "meaningless" names which give no indication of the purpose of the package? If anything which is in development were to be placed in this package then unrelated things may get mixed together. Remember about javadoc, there is even a file for package information, note that code is development code in the javadoc.
Also with distributed version control systems like mercurial, remember you can work in a local repository, committing there as much as you like, and only push to the central repository when you feel its ready for public consumption. Thus that also would get away from any concerns of people using code which is not ready.
Michael Whapples
