accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Elser <josh.el...@gmail.com>
Subject Re: [VOTE] Apache Accumulo 1.7.0 rc1
Date Mon, 11 May 2015 22:01:45 GMT
Christopher and I have been talking in chat about this.

Devs, please continue testing this release candidate. You can either 
remove the DEPENDENCIES file to validate that the source archive can 
still be built or just -Drat.skip. Christopher is doing some leg work to 
see if he can track down where that file is coming from -- the 
short-term fix is to just add DEPENDENCIES to rat ignore, but this also 
comes at the cost of the source archive not 100% matching the tag in git.

Josh Elser wrote:
> Isn't DEPENDENCIES generated by the Apache parent pom (or more
> accurately, something it enables)? I seem to recall that file being
> automatically generated in other projects.
>
> FWIW, I just used `assemble/build.sh --create-release-candidate` to
> generate everything, which, IMO, should be automated to do this for us.
>
> Christopher wrote:
>> All the hashes and sigs, and javadocs/sources look okay, but I saw a
>> few problems with the source tarball, which might be related to each
>> other:
>>
>> * The -src.tar.gz seems to have an extra file, "DEPENDENCIES", which
>> creates a rat failure when building from the src. I'm not sure how
>> this file got bundled with our source tarball.
>>
>> * The META-INF/MANIFEST.MF files in all the jars also have the
>> Implementation Build set to
>> "d8d682d53f348c8f1326eaa49c66672cb2e0b525-dirty". The "-dirty" should
>> have been fixed in ACCUMULO-3610 for the normal case. The only thing I
>> can think could be causing this (unless mavanagaiata 0.7.1 didn't
>> actually fix it), would be the presence of this extra DEPENDENCIES
>> file.
>>
>>
>> --
>> Christopher L Tubbs II
>> http://gravatar.com/ctubbsii
>>
>>
>> On Mon, May 11, 2015 at 12:26 PM, Josh Elser<josh.elser@gmail.com> wrote:
>>> One thing I noticed already is that I forgot to update the CHANGES file.
>>>
>>>
>>> Josh Elser wrote:
>>>> Devs,
>>>>
>>>> Please consider the following candidate for Apache Accumulo 1.7.0
>>>>
>>>> Tag: 1.7.0-rc1
>>>> SHA1: d8d682d53f348c8f1326eaa49c66672cb2e0b525
>>>> Staging Repository:
>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1028/
>>>>
>>>>
>>>> Source tarball:
>>>>
>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1028/org/apache/accumulo/accumulo/1.7.0/accumulo-1.7.0-src.tar.gz
>>>>
>>>>
>>>> Binary tarball:
>>>>
>>>> https://repository.apache.org/content/repositories/orgapacheaccumulo-1028/org/apache/accumulo/accumulo/1.7.0/accumulo-1.7.0-bin.tar.gz
>>>>
>>>>
>>>> (Append ".sha1", ".md5" or ".asc" to download the signature/hash for an
>>>> artifact.)
>>>>
>>>> Signing keys available at: https://www.apache.org/dist/accumulo/KEYS
>>>>
>>>> 1.7.0 includes 688 resolved issues:
>>>>
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312121&version=12324607
>>>>
>>>>
>>>>
>>>> Testing: All unit and integration tests are passing. Completed 3-day CI
>>>> w/o agitation and verification. Other tests still running.
>>>>
>>>> API compatibility report for 1.6.2 to 1.7.0:
>>>>
>>>> http://people.apache.org/~elserj/accumulo-1.7.0-rc1/1.6.2_to_1.7.0/compat_report.html
>>>>
>>>>
>>>>
>>>> API backwards compatibility report for 1.7.0 to 1.6.2:
>>>>
>>>> http://people.apache.org/~elserj/accumulo-1.7.0-rc1/1.7.0_to_1.6.2/compat_report.html
>>>>
>>>>
>>>>
>>>> Reports look fine to me; I believe we have source compatibility.
>>>>
>>>> The vote will be open until Thursday, May 15th 1:00AM ET. Here's my +1.

Mime
View raw message