Colin Sampaleanu <[EMAIL PROTECTED]> wrote on 19/09/2003 05:07:29 AM:
> I really like the idea of another public release which incorporates all > the fixes since b10. We all do. > Maybe I'm just being picky, but I think beta-11 is a much more > appropriate name than RC1. I'm just over the whole use of beta. Maven started off as a beta, and it was nowhere near feature complete. it is now though. > Release Candidate implies it's a candidate > for release, with generally no known bugs (non-trvial, anyways) which There are always known bugs :-) It's just how well other people know about them, and how important they are. > must be fixed before final release, and barring new bugs being found, 'Final' is a bit of misnomer to me. There will be no 'final' release of Maven. It's an ongoing work. > may even be released as the final version. As such, I don't think this > would really qualify. There are a number of serious issues to still > resolve (one affecting me for example, is that that inability of plugins > to support local (or remote) repo overrides via project.properties > completely breaks the multiproject plugin. Maybe some people wouldn't > agree that this is serious breakage, but if you need this feature you're > completely screwed...). This is a known bug, that we've lived with for a long time. But not one I see getting fixed for 1.0 @ this point. Bugs like this need to be fixed, but I don't see why we need to be 'bug free' for a 1.0 release. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
