Hi Benson,

Thanks for the comments.

On 11/06/12 15:16, Benson Margulies wrote:
I don't understand the remark about sdb and larq. Are you just noting
that the tag tags them even though you are not releasing them?

Yes. mvn release:* tags everything as in SVN so even though the build had had jena-sdb and jena-larq cleared out of the way, the tagging caught them.

So the SVN tag is a superset of the source-release - the SVN tagged source tree builds the same as the release (jena-sdb and jena-larq aren't in the module list of the top level POM).

Also, you need three PMC members, formally, not just three committers
(which is only important is the list is different).

Point taken.  In our case, it's not different.

        Andy




On Mon, Jun 11, 2012 at 9:44 AM, Andy Seaborne<[email protected]>  wrote:
Hi,

Here is a vote on a release build for Jena 2.7.1.

Everyone, not just committers, is invited to test and vote.
(We do need at least 3 committer +1's.)


This is a distribution of Jena (IRI, core, ARQ, TDB) and also of Fuseki.

Versions:

jena-parent     1
jena-iri        0.9.1
jena-core       2.7.1
jena-arq        2.9.1
jena-tdb        0.9.1
apache-jena     2.7.1 (the combined distribution)

jena-fuseki     0.2.2 (separate binary)

Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-222/

Proposed dist/ area:
http://people.apache.org/~andy/Jena-2.7.1/dist/

Keys:
https://svn.apache.org/repos/asf/jena/dist/KEYS

SVN tag:
https://svn.apache.org/repos/asf/jena/tags/jena-2.7.1/

NB. This picks up jena-sdb and jena-larq as well.
The source-release does not; jena-sdb and jena-larq are
not included in the build.


Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This vote will be open to the end of
Thursday 14/June 23:59 UTC
(72 hours from the same hour tonight UTC).

    Andy


Checking needed:

    is the GPG signature fine?
    is there a source archive?
    can the source archive really be built?
    is there a correct LICENSE and NOTICE file in each artifact
      (both source and binary artifacts)?
    does the NOTICE file contain all necessary attributions?
    check the dependencies.
    do all the tests work?
    if there is a tag in the SCM, does it contain reproducible sources?

Reply via email to