--- Martin Cooper <[EMAIL PROTECTED]> wrote: > > 1) Change ant/maven to exclude finder directory > (for 1.1, stays in CVS until > > worked on) > > Do we have concensus that it won't be part of 1.1? My understanding was that it wasn't finished, therefore exculsion was the most appropriate solution.
> > 2) Check all method names and signatures in > FilenameUtils (and any other > > class whose first release it is) > > What are we checking for, exactly? What I mean by this is 'does the API make sense?', 'are the method names the best they could be?'. Its not about coding standards. I include this because on lang and io previous releases we have released and then evaluated methods for common sense - we should try to do a QA review before release. > > 3) Decide on whether to merge WildcardUtils with > FilenameUtils > > How do we decide that? Why would we? Why would we > not? At present its MHO that [io] is best with utility classes focussed on what they work on. Thus, a class for Stream/WRiter/Reader (IOUtils), one for files (FileUtils) and one for filenames (FilenameUtils). WildcardUtils is task focussed, so doesn't fit this classification, so I would argue for it to be rolled into FilenameUtils. > > 4) Check whether there are any other method names > we got wrong in 1.0 and we > > want to fix now (like CopyUtils) > > Again, what are we checking for, exactly? See #2. To some degree this is gut feel based on how usable the library is in real life. > > 5) Check jdiff and clirr for compatability > > Hints on what this means would be appreciated, since > I have no clue... We must ensure that 1.1 is source and binary compatible with 1.0. We use jdiff and clirr to do this. Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
