+1, though I'm a little curious whether it would be better to simply try to release a 1.0. If this is good enough for a release candidate, and you've staged it where people can try it out, then this candidate could just be pushed out as a final release if nobody reports a problem...
How long of a "soak" period do you feel would be appropriate for this release candidate, before we can be sure it's ready to be -final? -john On 4/13/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
+1 On 4/13/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > Hi, > > I'd like to release Maven SCM 1.0-rc1 > This version fix few bugs, add a new provider (mercurial) and few commands. > > Road Map: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&styleName=Html&version=13066 > > Site: > http://people.apache.org/~evenisse/stage/site/ > > Staging repo: > http://people.apache.org/~evenisse/stage/repo/ > > Tag: > http://svn.apache.org/repos/asf/maven/scm/tags/maven-scm-1.0-rc1/ > > So, let's try 72h +1/+0/-1. Please cast your votes! > > Here my +1 > > Emmanuel > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride
