I assume this is also a problem within maven-scm-1.0, isn't? So releasing maven-scm-1.1 doesn't make it worse, and we should address this issue in 1.1.1
Only my private opinion, but as someone already mentioned, if we wait for all errors to be fixed, then we'll never get anything released. LieGrü, strub --- ChrisGWarp <[EMAIL PROTECTED]> schrieb am Mo, 25.8.2008: > Von: ChrisGWarp <[EMAIL PROTECTED]> > Betreff: Re: [VOTE] Release Maven Scm 1.1 (take 3) > An: scm-dev@maven.apache.org > Datum: Montag, 25. August 2008, 1:23 > -1 > > Not until SCM-392 has been fixed. This is a critical issue > for us. > > And I don't imagine that it is that an uncommon a > problem either. > > http://jira.codehaus.org/browse/SCM-392 > > -Chris > > -- > View this message in context: > http://www.nabble.com/-VOTE--Release-Maven-Scm-1.1-%28take-3%29-tp19123852p19135931.html > Sent from the Maven - SCM mailing list archive at > Nabble.com. __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
