+1 on the understanding that the SDO API use of the OSOA licensed code is clarified before we try to graduate.
I think the SDO API Maven artifacts are missing from the staging repository so there will need to a vote update if we're releasing that. And I think it would be better and easier to merge all the distros into just src and binary distros and use the Maven assembly plugin to generate them, if it will help I'll volunteer to sort that out for the next release? ...ant On 4/26/07, kelvin goodson <[EMAIL PROTECTED]> wrote:
Please vote to release the beta1 distribution of Tuscany SDO for Java The release candidate RC1 for Tuscany Java SDO beta1 archive distribution files are posted here at [1] The maven repository artifacts are posted in a staging repository [2] <http://people.apache.org/%7Ekelvingoodson/sdo_java/M3/RC2/>The release audit tool (rat) files and associated exceptions are attached to the jira under which the release work was done is at [3]. <http://issues.apache.org/jira/browse/TUSCANY-1171> The tag for the source code is at [4] Changes in this release are shown in [5]< http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubator-M3/sdo/distribution/RELEASE_NOTES.txt > [1] http://people.apache.org/~kelvingoodson/sdo_java/beta1/RC1/ [2] http://people.apache.org/~kelvingoodson/repo/org/apache/tuscany/sdo/ [3] http://issues.apache.org/jira/browse/TUSCANY-1171 [4] http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/ [5] http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.0-incubating-beta1/sdo/distribution/RELEASE_NOTES.txt Thanks in advance, Kelvin.
