The vote passed with no objection and 3 binding +1 (Enrico, Rupert, Reto). I will proceed with the release.
Reto On Mon, Mar 23, 2015 at 11:02 AM, Andy Seaborne <[email protected]> wrote: > On 23/03/15 09:58, Reto Gmür wrote: > >> Hi Stian, >> >> On Mon, Mar 23, 2015 at 9:49 AM, Stian Soiland-Reyes <[email protected]> >> wrote: >> >> Not sure we can do lazy consensus voting on releases? >>> >> > I'm glad to see that there are going to be enough votes for the release by > majority vote. > > If the result message (without "lazy consensus" in the title), as normal, > mentions the 3 +1 binding, things should be good to go. > > I've seen it done in other projects: >> >> http://mail-archives.apache.org/mod_mbox/commons-dev/201501.mbox/% >> 3CCAOGo0VYGktw2QszaEX0MsXDz-0T0UzqwjBkJn=gfacd8ouf...@mail.gmail.com%3E >> > > The only examples that I could find anywhere in ASF are that one and the > old way that Cordova used to release, which has now changed. > > I guess we could have a PMC vote if we think that's a good thing to do. >> > > As background: > > http://www.apache.org/dev/release.html#approving-a-release > > which is policy page. > > """ > Votes on whether a package is ready to be released use majority approval > -- i.e., at least three PMC members must vote affirmatively for release, > and there must be more positive than negative votes. Releases may not be > vetoed. Before voting +1 PMC members are required to download the signed > source code package, compile it as provided, and test the resulting > executable on their own platform, along with also verifying that the > package meets the requirements of the ASF policy on releases. > """ > > "majority approval" is defined terminology. > > PMC members have to take certain steps in a release vote. > > Andy > > > >> >> >>> https://www.apache.org/dev/release.html#approving-a-release >>> >>> .. but adding yourself, we would have +3 PMC already. >>> >>> >> +1 :) >> >> >> >>> >>> My +0 (non-binding) >>> >>> >>> To test this I modified */pom.xml of the tag to use the new parent. >>> >>> >>> I then got: >>> >>> [ERROR] The project >>> org.apache.clerezza:rdf.jena.commons:1.0.0-SNAPSHOT >>> (/home/stain/src/clerezza/rdf.jena.commons/pom.xml) has 1 error >>> [ERROR] 'dependencies.dependency.version' for >>> org.apache.jena:jena-core:jar is missing. @ line 42, column 21 >>> [ERROR] >>> [ERROR] The project >>> org.apache.clerezza:rdf.jena.sparql:1.0.0-SNAPSHOT >>> (/home/stain/src/clerezza/rdf.jena.sparql/pom.xml) has 1 error >>> [ERROR] 'dependencies.dependency.version' for >>> org.apache.jena:jena-arq:jar is missing. @ line 47, column 21 >>> [ERROR] >>> [ERROR] The project >>> org.apache.clerezza:rdf.jena.tdb.storage:1.0.0-SNAPSHOT >>> (/home/stain/src/clerezza/rdf.jena.tdb.storage/pom.xml) has 1 error >>> [ERROR] 'dependencies.dependency.version' for >>> org.apache.jena:jena-tdb:jar is missing. @ line 73, column 21 >>> >>> >>> This was previously in <dependencyManagement> of the parent. >>> Should it not still be there? >>> >>> stain@biggie-utopic:~/src/clerezza/parent$ grep jena pom.xml >>> stain@biggie-utopic:~/src/clerezza/parent$ >>> >>> >> Yes, the dependecy has been removed as it caused problems where fuseki is >> used in tests. The problem with dependency management is that it also >> affects indirect dependencies. So in the case of fuseki the version of >> fuseki was explicitely declared but things didn't work at runtime as >> fuseki >> got some incompatible dependencies. >> >> I think a better way is to use dedicated dependency management projects >> like this here: >> >> https://git-wip-us.apache.org/repos/asf?p=clerezza.git;a=tree;f=rdf/jena/ >> dependencymanagement;h=89bc7093eab019b44a0ebe28b14706 >> 41f326f014;hb=refs/heads/rdf-commons >> >> So projects that want to use the jena dependendies in the same versions as >> other modules can import this in their dependency management. >> >> >> Cheers, >> Reto >> >> >> >> >> >>> >>> (Not a -1 as this could be fixed locally instead). >>> >>> On 21 March 2015 at 11:41, Reto Gmür <[email protected]> wrote: >>> >>>> The Apache Clerezza Parent has been updated to use Java 8. Dependency >>>> versions have been updated and the scr plugin causing problems in >>>> >>> non-OSGi >>> >>>> projects has been removed >>>> >>>> This is a VOTE to release Clerezza Parent 6. >>>> >>>> This VOTE by LAZY-CONSENSUS is open for at least 72 hours until March 24 >>>> 12:00 UTC. >>>> >>>> The tag in git is: clerezza-parent-6 >>>> >>>> The source release is here: >>>> >>>> >>>> https://repository.apache.org/content/repositories/ >>> orgapacheclerezza-1003/org/apache/clerezza/clerezza/6/ >>> clerezza-6-source-release.zip >>> >>>> >>>> The signature is here: >>>> >>>> >>>> https://repository.apache.org/content/repositories/ >>> orgapacheclerezza-1003/org/apache/clerezza/clerezza/6/ >>> clerezza-6-source-release.zip.asc >>> >>>> >>>> >>>> md5sum clerezza-6-source-release.zip >>>> 154c6ac4803f6d821a54388b82fa1783 clerezza-6-source-release.zip >>>> >>>> >>>> The keys are here: >>>> https://dist.apache.org/repos/dist/release/clerezza/KEYS >>>> >>>> >>>> Reto >>>> >>> >>> >>> >>> -- >>> Stian Soiland-Reyes >>> Apache Taverna (incubating), Apache Commons RDF (incubating) >>> http://orcid.org/0000-0001-9842-9718 >>> >>> >> >
