struberg wrote:
>
> 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
>
All valid comments.
I guess my main concerns are:
1. This is a major show stopper for us (so I think that it should be
included, with a heavy weighting because of point 2).
2. Do I have to wait another 18 months before 1.1.1? I will have given up on
maven well before then if so.
-Chris
--
View this message in context:
http://www.nabble.com/-VOTE--Release-Maven-Scm-1.1-%28take-3%29-tp19123852p19142346.html
Sent from the Maven - SCM mailing list archive at Nabble.com.
