I regret but I have to vote: -1 non binding My main reason for this is the existence of hard code depency numbers. As we are using taverna parent to provided version numbers this should be done completely consistant. Some place hard coded numbers where found are taverna-scufl2-examples
Also several poms have hard coded number in the <build> section. This is less critical but why not be consistant. I also read comments regarding Licence, notice disclaimer ect which should be address in this the first release. On the plus side the code did build and test. I noticed that Baclava support was still included and wondered why? Should this package and the classes at the very least not be marked Depricated? Christian ________________________________________ From: Stian Soiland-Reyes [[email protected]] Sent: Thursday, June 11, 2015 3:48 PM To: [email protected] Subject: [VOTE] Release Apache Taverna Language 0.15.0-incubating RC2 I am pleased to be calling this vote for the source release of Apache Taverna Maven Parent 1-incubating Apache Taverna Language 0.15.0-incubating Apache Taverna Language is a set of APIs for workflow definitions (SCUFL2) and workflow inputs/outputs/run (DataBundle), as consumed and produced by the Apache Taverna workflow system. The API includes support for working with Research Object Bundles, and loading/saving Taverna workflows in different formats. The release candidates to be voted over are available at: https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-parent-1-incubating-RC2/ https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-language-0.15.0-incubating-RC2/ SHA-1 checksums: 8199880048a59cde622e0caa24c3bc3d83bc5d5a taverna-parent-1-incubating-source-release.zip 7032e9d2be834f7c029aae562b62613481bf6939 taverna-language-0.15.0-incubating-source-release.zip MD5 checksums: 7f9b107b9f1dc0407783ac0ad484d6ea taverna-parent-1-incubating-source-release.zip 35d3085b596b2dd4b30a0234259efade taverna-language-0.15.0-incubating-source-release.zip Build the release candidate in the above order, using: mvn clean install The release candidates correspond to the following git commits: https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-maven-parent.git;a=commit;h=3ba669c78782d3fc3b548e2a512d201ee922b34a https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-language.git;a=commit;h=3340e2090e604b40ac0b88675f57c1d12032d060 Release candidates are signed with a GPG key available at: https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachetaverna-1003/ The changelog for this release is available from JIRA: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322&version=12332247 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322&version=12332246 Please vote on releasing these packages as: Apache Taverna Maven Parent 1-incubating Apache Taverna Language 0.1.0-incubating The vote is open for at least 72 hours and passes if a majority of at least three +1 Apache Taverna PPMC votes are cast. [ ] +1 Release this package [ ] 0 I don't feel strongly about it, but don't object [ ] -1 Do not release this package because... Anyone can participate in testing and voting, not just committers, please feel free to try out the release candidate and provide your votes. (Before anyone asks, RC1 was a release candidate tag I dropped as it used an older Apache super-pom) -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
