Re: [VOTE] Release Apache Joshua 6.1 (Incubating) RC4

[lewis john mcgibbney]

Hi Folks,
I generated it by simply copying the JIRA report into CHANGES.md. It turns
out that this looks somewhat nice due to markdown rendering!
No real work involved... so I can;t take credit for anything :(
I'll get on to the release ASAP.
Thanks

On Mon, May 8, 2017 at 6:04 AM, Tommaso Teofili 
wrote:

> Hi Henry,
>
> I just took the one created by Lewis, so he should know :-)
>
> Regards,
> Tommaso
>
> Il giorno gio 4 mag 2017 alle ore 20:39 Henry Saputra <
> henry.sapu...@gmail.com> ha scritto:
>
>> Hi Tommaso, curious how did you generate the CHANGES.md for the release
>> note?
>>
>> Was it manually created by looking at the JIRA tickets and Git PR merges?
>>
>> Thanks,
>>
>> - Henry
>>
>> On Thu, Mar 9, 2017 at 5:40 AM, Tommaso Teofili <
>> tommaso.teof...@gmail.com>
>> wrote:
>>
>> > Hi Folks,
>> > Please VOTE on the Apache Joshua 6.1 Release Candidate #4.
>> >
>> > We solved 36 issues:
>> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> > projectId=12319720=12335049
>> >
>> > Git source tag (23d5bda277028ea42b142b221639fd233a08da36):
>> > https://git-wip-us.apache.org/repos/asf?p=incubator-joshua.
>> git;a=commit;h=
>> > 23d5bda277028ea42b142b221639fd233a08da36
>> >
>> > Staging repo:
>> > https://repository.apache.org/content/repositories/orgapachejoshua-1005
>> >
>> > Source Release Artifacts:
>> > https://dist.apache.org/repos/dist/dev/incubator/joshua/6.1/
>> >
>> > PGP release keys (signed using 891768A5):
>> > *https://git1-us-west.apache.org/repos/asf?p=incubator-
>> > joshua.git;a=blob_plain;f=KEYS;h=aa18365bf5c8c8fb17b084f783a75c
>> > 3a2460a98d;hb=HEAD
>> > > > joshua.git;a=blob_plain;f=KEYS;h=aa18365bf5c8c8fb17b084f783a75c
>> > 3a2460a98d;hb=HEAD>*
>> >
>> > Vote will be open for 72 hours.
>> > Thank you to everyone that is able to VOTE as well as everyone that
>> > contributed to Apache Joshua 6.1.
>> >
>> > [ ] +1, let's get it released!!!
>> > [ ] +/-0, fine, but consider to fix few issues before...
>> > [ ] -1, nope, because... (and please explain why)
>> >
>> > Regards,
>> > Tommaso
>> >
>>
>


-- 
http://home.apache.org/~lewismc/
@hectorMcSpector
http://www.linkedin.com/in/lmcgibbney

Re: [RESULT] [VOTE] Release Apache Joshua 6.1 (Incubating) RC4

[Tom Barber]

Good work Tommaso!

On Wed, May 3, 2017 at 9:27 AM, Tommaso Teofili 
wrote:

> Hi Everyone,
>  As the 72 hours period has come and gone I would like to bring this thread
> to a close.
> The VOTE's have been counted and RESULT's are as follows:
>
> - [4] +1, let's get it released!!!
> Tommaso Teofili *
> Lewis John McGibbney *
> Matt Post *
> John Hewitt *
>
> - [0] +/-0, fine, but consider to fix few issues before...
> - [0] -1, nope, because... (and please explain why)
>
>  *Joshua PMC Binding VOTE
>  I'll progress with the remainder of the release procedure.
>
>  Regards,
>  Tommaso
>



-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim 

Schedule a meeting with me 

GB: +44(0)5603641316
US: +18448141689

Re: [VOTE] Release Apache Joshua 6.1 (Incubating) RC4

[Matt Post]

+1

✓ MD5 sums (tar and zip)
✓ includes DISCLAIMER
✓ build from src distribution (zip and tgz): 168 tests run, 31 skipped
✓ verified both GPG signatures

I agree about Michael's earlier point: the file name is 
joshua-incubating-6.1-src.tar.gz but it unpacks to 
apache-joshua-incubating-6.1. This discrepancy is okay for now but should be 
fixed in the future.

(at some point when we're in person we should exchange GPG keys)

matt

> On Mar 20, 2017, at 9:53 PM, Matt Post  wrote:
> 
> Folks — This is still in my queue so let's keep this open.
> 
> matt
> 
> 
>> On Mar 16, 2017, at 8:56 PM, John Hewitt  wrote:
>> 
>> Lewis is right about the week. Sorry, everyone. This week had a DARPA
>> meeting in Atlanta. I'll get my +/-1 out tomorrow.
>> 
>> -John
>> 
>> On Thu, Mar 16, 2017 at 8:53 PM, Michael A. Hedderich <
>> m...@michael-hedderich.de> wrote:
>> 
>>> Hi,
>>> 
>>> Thanks Tommaso for putting the release together!
>>> 
>>> I was traveling to the US, sorry for the delay from my side.
>>> 
>>> Here is my list:
>>> - build from tag: passed
>>> - build from staging repo (zip and gz): passed
>>> - build from source release artifacts (zip and gz): passed
>>> - md5, sha1 and acc match within the stagging repo
>>> - md5 and acc match within the source release artifacts
>>> 
>>> What does not match for me are the md5 or sha1 of the stagging repo with
>>> those of the source release artifacts. E.g.
>>> https://repository.apache.org/content/repositories/
>>> orgapachejoshua-1005/org/apache/joshua/joshua-incubating/6.1/joshua-
>>> incubating-6.1-src.tar.gz.md5
>>> vs
>>> https://dist.apache.org/repos/dist/dev/incubator/joshua/6.1/
>>> joshua-incubating-6.1-src.tar.gz.md5
>>> 
>>> Is this the expected behavior?
>>> 
>>> The link to the check-list that Tom Barber had sent around in the past (
>>> http://incubator.apache.org/guides/releasemanagement.html#check-list) does
>>> not seem to be valid anymore. At least for me the anchor point does not
>>> work and I could not find the check-list on this page or one of its
>>> subpages. Does anyone know if this list still exists? If not, should we put
>>> such a list on the Joshua PPMC Wiki?
>>> 
>>> Regards,
>>> Michael
>>> 
>>> 
>>> 2017-03-16 20:11 GMT-04:00 lewis john mcgibbney :
>>> 
 Hi Tommaso,
 It looks like you caught the PPMC on a bad week... we will get the VOTE'd
 done worry ;)
 Thanks for putting the RC together.
 Comments inline
 
 On Mon, Mar 13, 2017 at 3:58 PM, <
 dev-digest-h...@joshua.incubator.apache.org> wrote:
 
 SIGS look good so do tags and staging repos.
 
 On primary release src at
 https://dist.apache.org/repos/dist/dev/incubator/joshua/6.1/
 joshua-incubating-6.1-src.tar.gz,
 the compressed archive is called joshua-incubating-6.1-src, when I
 decompress it, it is called apache-joshua-6.1-incubating. This is a minor
 inconsistency which we may wish to address for next incubating release.
 
 When I build (mvn clean install) I get the following... damn laptop. This
 is the same issue I got when I tried to spin the original RC2 myself.
>>> This
 is specific to my environment s not a blocker.
 
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 29.351 s
 [INFO] Finished at: 2017-03-16T17:07:16-07:00
 [INFO] Final Memory: 41M/697M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single
 (source-release-assembly) on project joshua-incubating: Execution
 source-release-assembly of goal
 org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single failed: user
 id
 '498339010' is too big ( > 2097151 ). -> [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>> -e
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/
>>> PluginExecutionException
 
 A mvn clean test results in the following
 
 [INFO]
 
 [INFO] BUILD SUCCESS
 [INFO]
 
 [INFO] Total time: 18.971 s
 [INFO] Finished at: 2017-03-16T17:09:25-07:00
 [INFO] Final Memory: 34M/608M
 [INFO]
 
 
 CHANGES, DISCLAIMER, LICENSE, NOTICE and README all look good. DOAP is

Re: [VOTE] Release Apache Joshua 6.1 (Incubating) RC4

[Matt Post]

Folks — This is still in my queue so let's keep this open.

matt


> On Mar 16, 2017, at 8:56 PM, John Hewitt  wrote:
> 
> Lewis is right about the week. Sorry, everyone. This week had a DARPA
> meeting in Atlanta. I'll get my +/-1 out tomorrow.
> 
> -John
> 
> On Thu, Mar 16, 2017 at 8:53 PM, Michael A. Hedderich <
> m...@michael-hedderich.de> wrote:
> 
>> Hi,
>> 
>> Thanks Tommaso for putting the release together!
>> 
>> I was traveling to the US, sorry for the delay from my side.
>> 
>> Here is my list:
>> - build from tag: passed
>> - build from staging repo (zip and gz): passed
>> - build from source release artifacts (zip and gz): passed
>> - md5, sha1 and acc match within the stagging repo
>> - md5 and acc match within the source release artifacts
>> 
>> What does not match for me are the md5 or sha1 of the stagging repo with
>> those of the source release artifacts. E.g.
>> https://repository.apache.org/content/repositories/
>> orgapachejoshua-1005/org/apache/joshua/joshua-incubating/6.1/joshua-
>> incubating-6.1-src.tar.gz.md5
>> vs
>> https://dist.apache.org/repos/dist/dev/incubator/joshua/6.1/
>> joshua-incubating-6.1-src.tar.gz.md5
>> 
>> Is this the expected behavior?
>> 
>> The link to the check-list that Tom Barber had sent around in the past (
>> http://incubator.apache.org/guides/releasemanagement.html#check-list) does
>> not seem to be valid anymore. At least for me the anchor point does not
>> work and I could not find the check-list on this page or one of its
>> subpages. Does anyone know if this list still exists? If not, should we put
>> such a list on the Joshua PPMC Wiki?
>> 
>> Regards,
>> Michael
>> 
>> 
>> 2017-03-16 20:11 GMT-04:00 lewis john mcgibbney :
>> 
>>> Hi Tommaso,
>>> It looks like you caught the PPMC on a bad week... we will get the VOTE'd
>>> done worry ;)
>>> Thanks for putting the RC together.
>>> Comments inline
>>> 
>>> On Mon, Mar 13, 2017 at 3:58 PM, <
>>> dev-digest-h...@joshua.incubator.apache.org> wrote:
>>> 
>>> SIGS look good so do tags and staging repos.
>>> 
>>> On primary release src at
>>> https://dist.apache.org/repos/dist/dev/incubator/joshua/6.1/
>>> joshua-incubating-6.1-src.tar.gz,
>>> the compressed archive is called joshua-incubating-6.1-src, when I
>>> decompress it, it is called apache-joshua-6.1-incubating. This is a minor
>>> inconsistency which we may wish to address for next incubating release.
>>> 
>>> When I build (mvn clean install) I get the following... damn laptop. This
>>> is the same issue I got when I tried to spin the original RC2 myself.
>> This
>>> is specific to my environment s not a blocker.
>>> 
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 29.351 s
>>> [INFO] Finished at: 2017-03-16T17:07:16-07:00
>>> [INFO] Final Memory: 41M/697M
>>> [INFO]
>>> 
>>> [ERROR] Failed to execute goal
>>> org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single
>>> (source-release-assembly) on project joshua-incubating: Execution
>>> source-release-assembly of goal
>>> org.apache.maven.plugins:maven-assembly-plugin:3.0.0:single failed: user
>>> id
>>> '498339010' is too big ( > 2097151 ). -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e
>>> switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> [ERROR] [Help 1]
>>> http://cwiki.apache.org/confluence/display/MAVEN/
>> PluginExecutionException
>>> 
>>> A mvn clean test results in the following
>>> 
>>> [INFO]
>>> 
>>> [INFO] BUILD SUCCESS
>>> [INFO]
>>> 
>>> [INFO] Total time: 18.971 s
>>> [INFO] Finished at: 2017-03-16T17:09:25-07:00
>>> [INFO] Final Memory: 34M/608M
>>> [INFO]
>>> 
>>> 
>>> CHANGES, DISCLAIMER, LICENSE, NOTICE and README all look good. DOAP is
>>> slightly out of date, however it reflects the first RC.
>>> 
>>> 
>>> [X] +1, let's get it released!!!
 
>>> 
>>> Thank you Tommaso
>>> 
>>> --
>>> http://home.apache.org/~lewismc/
>>> @hectorMcSpector
>>> http://www.linkedin.com/in/lmcgibbney
>>> 
>> 

Re: [VOTE] Release Apache Joshua 6.1 (Incubating)

[Matt Post]

Tommaso,

What's your timeline for fixing this? I just pushed in some changes that add 
docker support and provide multithreading for the HTTP server. It would be nice 
to include those, BUT if it's a lot of extra work, we can just add them later 
(or you could point me to the doc you followed, and I'll do it on Monday)

matt


> On Mar 1, 2017, at 1:09 PM, John Hewitt  wrote:
> 
> Tommaso, thanks for the RC.
> Kellen, thanks for checking for the -1.
> 
> -John
> 
> On Wed, Mar 1, 2017 at 1:03 PM, kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
> 
>> For a short term fix for the unit test we can delete lines 48 and 50 from
>> LMGrammarBerkeleyTest.java.
>> 
>> A bit of a longer term solution would be that we could have a @BeforeClass
>> setup method that simply zips the uncompressed files.
>> 
>> Thanks again for putting this together Tommaso.
>> 
>> 
>> On Wed, Mar 1, 2017 at 6:43 PM, Tommaso Teofili >> 
>> wrote:
>> 
>>> thanks Kellen,
>>> 
>>> I get the very same issues.
>>> It's probably my fault having copied .md5 and .sha files from the staging
>>> repo as I didn't have them within my target directory.
>>> I also get the same test failure.
>>> 
>>> Hence -1 from me too.
>>> I'll roll it back, fix the issues and create RC4.
>>> 
>>> Regards,
>>> Tommaso
>>> 
>>> 
>>> 
>>> Il giorno mer 1 mar 2017 alle ore 17:54 kellen sunderland <
>>> kellen.sunderl...@gmail.com> ha scritto:
>>> 
 I have to -1 this release for the time being.  For me the signatures
>> and
 hashes don't seem to match the binaries downloaded.  Could you double
>>> check
 that they match for you Tommaso?  I'm also getting a unit test that
>> fails
 when I run 'mvn clean package'.  I'm digging a little more into this
>> one,
 but suspect a missing file.
 
 
 
 Here's what I've checked so far:
 
 Release artifacts must include incubating in the final file name - YES
 Release artifacts must include a disclaimer within the release
>>> artifact(s)
 as noted - YES
 Every ASF release MUST contain one or more source packages, which MUST
>> be
 sufficient for a user to build and test the release provided they have
 access to the appropriate platform and tools. - NO
-Not building due to failing test (BerkleyLM failure).  I'm
>> digging a
 bit more into this.
 
 Every artifact distributed to the public through Apache channels MUST
>> be
 accompanied by one file containing an OpenPGP compatible ASCII armored
 detached signature and another file containing an MD5 checksum.
- .asc - NO
I get warning:
"gpg --verify joshua-incubating-6.1-src.tar.gz.asc
 joshua-incubating-6.1-src.tar.gz
gpg: Signature made Thu Feb 23 09:15:17 2017 CET using RSA key ID
 891768A5
gpg: Good signature from "Tommaso Teofili "
 [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to
>>> the
 owner."
- .md5 - NO
My md5 of joshua-incubating-6.1-src.tar.gz is
 504976876b01294811293aa45b5400f5, the joshua-incubating-6.1-src.tar.
>>> gz.md5
 indicates it should be 22b738eeae45757715080702a5bd2789
- .sha - NO
My sha of joshua-incubating-6.1-src.tar.gz is
 4AB5BA24301590F36AE6452DACC3F21CBD8B3FEC, the
 joshua-incubating-6.1-src.tar.gz.md5 indicates it should be
 2a55b6d341dddc5369b22a4802a86ec40accd0a1
- KEYS - YES
 
 On Mon, Feb 27, 2017 at 3:55 AM, Matt Post  wrote:
 
> Hi folks,
> 
> First, Tommaso, thank you for pulling this together!
> 
> I want to remind everyone that there's a checklist to go through
>> before
> sending your +1. Here's from an email from Tom Barber a while back:
> 
>> Hello folks,
>> 
>> I see plenty of +1's going through the release vote,  which is
>> great
>>> to
> see
>> people taking an active role in getting the release shipped.
>> 
>> For those of you who are new to the ASF there are a bunch of
 requirements
>> to sign off for a release which you can find here:
>> 
>> http://incubator.apache.org/guides/releasemanagement.html#
>> check-list
>>> <
> http://incubator.apache.org/guides/releasemanagement.html#check-list
>>> 
>> 
>> My current concern is that people who are new to the incubator are
 +1'ing
>> software for release without check all or part of the release
>> cycle.
> Whilst
>> not mandatory, when you +1 a release please can you try to indicate
 what
>> you've checked. The reason for this is,  the tag Lewis has built
>> off
> isn't
>> the tip of master, so if you're basing  your +1 on your day to day
>> development and knowledge of the code base, that's not always whats
>> shipped. Also 

Re: [VOTE] Release Apache Joshua 6.1 (Incubating)

[kellen sunderland]

For a short term fix for the unit test we can delete lines 48 and 50 from
LMGrammarBerkeleyTest.java.

A bit of a longer term solution would be that we could have a @BeforeClass
setup method that simply zips the uncompressed files.

Thanks again for putting this together Tommaso.


On Wed, Mar 1, 2017 at 6:43 PM, Tommaso Teofili 
wrote:

> thanks Kellen,
>
> I get the very same issues.
> It's probably my fault having copied .md5 and .sha files from the staging
> repo as I didn't have them within my target directory.
> I also get the same test failure.
>
> Hence -1 from me too.
> I'll roll it back, fix the issues and create RC4.
>
> Regards,
> Tommaso
>
>
>
> Il giorno mer 1 mar 2017 alle ore 17:54 kellen sunderland <
> kellen.sunderl...@gmail.com> ha scritto:
>
> > I have to -1 this release for the time being.  For me the signatures and
> > hashes don't seem to match the binaries downloaded.  Could you double
> check
> > that they match for you Tommaso?  I'm also getting a unit test that fails
> > when I run 'mvn clean package'.  I'm digging a little more into this one,
> > but suspect a missing file.
> >
> >
> > 
> > Here's what I've checked so far:
> >
> > Release artifacts must include incubating in the final file name - YES
> > Release artifacts must include a disclaimer within the release
> artifact(s)
> > as noted - YES
> > Every ASF release MUST contain one or more source packages, which MUST be
> > sufficient for a user to build and test the release provided they have
> > access to the appropriate platform and tools. - NO
> > -Not building due to failing test (BerkleyLM failure).  I'm digging a
> > bit more into this.
> >
> > Every artifact distributed to the public through Apache channels MUST be
> > accompanied by one file containing an OpenPGP compatible ASCII armored
> > detached signature and another file containing an MD5 checksum.
> > - .asc - NO
> > I get warning:
> > "gpg --verify joshua-incubating-6.1-src.tar.gz.asc
> > joshua-incubating-6.1-src.tar.gz
> > gpg: Signature made Thu Feb 23 09:15:17 2017 CET using RSA key ID
> > 891768A5
> > gpg: Good signature from "Tommaso Teofili "
> > [unknown]
> > gpg: WARNING: This key is not certified with a trusted signature!
> > gpg:  There is no indication that the signature belongs to
> the
> > owner."
> > - .md5 - NO
> > My md5 of joshua-incubating-6.1-src.tar.gz is
> > 504976876b01294811293aa45b5400f5, the joshua-incubating-6.1-src.tar.
> gz.md5
> > indicates it should be 22b738eeae45757715080702a5bd2789
> > - .sha - NO
> > My sha of joshua-incubating-6.1-src.tar.gz is
> > 4AB5BA24301590F36AE6452DACC3F21CBD8B3FEC, the
> > joshua-incubating-6.1-src.tar.gz.md5 indicates it should be
> > 2a55b6d341dddc5369b22a4802a86ec40accd0a1
> > - KEYS - YES
> >
> > On Mon, Feb 27, 2017 at 3:55 AM, Matt Post  wrote:
> >
> > > Hi folks,
> > >
> > > First, Tommaso, thank you for pulling this together!
> > >
> > > I want to remind everyone that there's a checklist to go through before
> > > sending your +1. Here's from an email from Tom Barber a while back:
> > >
> > > > Hello folks,
> > > >
> > > > I see plenty of +1's going through the release vote,  which is great
> to
> > > see
> > > > people taking an active role in getting the release shipped.
> > > >
> > > > For those of you who are new to the ASF there are a bunch of
> > requirements
> > > > to sign off for a release which you can find here:
> > > >
> > > > http://incubator.apache.org/guides/releasemanagement.html#check-list
> <
> > > http://incubator.apache.org/guides/releasemanagement.html#check-list>
> > > >
> > > > My current concern is that people who are new to the incubator are
> > +1'ing
> > > > software for release without check all or part of the release cycle.
> > > Whilst
> > > > not mandatory, when you +1 a release please can you try to indicate
> > what
> > > > you've checked. The reason for this is,  the tag Lewis has built off
> > > isn't
> > > > the tip of master, so if you're basing  your +1 on your day to day
> > > > development and knowledge of the code base, that's not always whats
> > > > shipped. Also in the branching process,  its possible merges or
> > > alterations
> > > > were accidentally made that Lewis has missed (this is very unlikely I
> > > know
> > > > but you know, code changes). Also people build software on different
> > > OS's,
> > > > versions of OS's etc so just because it builds on  Lewis's laptop
> > doesn't
> > > > mean it builds on mine, for example.
> > > >
> > > > Also regarding licenses, disclaimers etc, people notice different
> > things
> > > or
> > > > interpret stuff differently. its always possible that someone might
> > miss
> > > a
> > > > library etc so its important multiple eyes run over the same stuff.
> > > >
> > > > Cheers,
> > > >
> > > > Tom
> > >
> > > I'm hoping I'll have time to go through this 

Re: [VOTE] Release Apache Joshua 6.1 (Incubating)

[Tommaso Teofili]

thanks Kellen,

I get the very same issues.
It's probably my fault having copied .md5 and .sha files from the staging
repo as I didn't have them within my target directory.
I also get the same test failure.

Hence -1 from me too.
I'll roll it back, fix the issues and create RC4.

Regards,
Tommaso



Il giorno mer 1 mar 2017 alle ore 17:54 kellen sunderland <
kellen.sunderl...@gmail.com> ha scritto:

> I have to -1 this release for the time being.  For me the signatures and
> hashes don't seem to match the binaries downloaded.  Could you double check
> that they match for you Tommaso?  I'm also getting a unit test that fails
> when I run 'mvn clean package'.  I'm digging a little more into this one,
> but suspect a missing file.
>
>
> 
> Here's what I've checked so far:
>
> Release artifacts must include incubating in the final file name - YES
> Release artifacts must include a disclaimer within the release artifact(s)
> as noted - YES
> Every ASF release MUST contain one or more source packages, which MUST be
> sufficient for a user to build and test the release provided they have
> access to the appropriate platform and tools. - NO
> -Not building due to failing test (BerkleyLM failure).  I'm digging a
> bit more into this.
>
> Every artifact distributed to the public through Apache channels MUST be
> accompanied by one file containing an OpenPGP compatible ASCII armored
> detached signature and another file containing an MD5 checksum.
> - .asc - NO
> I get warning:
> "gpg --verify joshua-incubating-6.1-src.tar.gz.asc
> joshua-incubating-6.1-src.tar.gz
> gpg: Signature made Thu Feb 23 09:15:17 2017 CET using RSA key ID
> 891768A5
> gpg: Good signature from "Tommaso Teofili "
> [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner."
> - .md5 - NO
> My md5 of joshua-incubating-6.1-src.tar.gz is
> 504976876b01294811293aa45b5400f5, the joshua-incubating-6.1-src.tar.gz.md5
> indicates it should be 22b738eeae45757715080702a5bd2789
> - .sha - NO
> My sha of joshua-incubating-6.1-src.tar.gz is
> 4AB5BA24301590F36AE6452DACC3F21CBD8B3FEC, the
> joshua-incubating-6.1-src.tar.gz.md5 indicates it should be
> 2a55b6d341dddc5369b22a4802a86ec40accd0a1
> - KEYS - YES
>
> On Mon, Feb 27, 2017 at 3:55 AM, Matt Post  wrote:
>
> > Hi folks,
> >
> > First, Tommaso, thank you for pulling this together!
> >
> > I want to remind everyone that there's a checklist to go through before
> > sending your +1. Here's from an email from Tom Barber a while back:
> >
> > > Hello folks,
> > >
> > > I see plenty of +1's going through the release vote,  which is great to
> > see
> > > people taking an active role in getting the release shipped.
> > >
> > > For those of you who are new to the ASF there are a bunch of
> requirements
> > > to sign off for a release which you can find here:
> > >
> > > http://incubator.apache.org/guides/releasemanagement.html#check-list <
> > http://incubator.apache.org/guides/releasemanagement.html#check-list>
> > >
> > > My current concern is that people who are new to the incubator are
> +1'ing
> > > software for release without check all or part of the release cycle.
> > Whilst
> > > not mandatory, when you +1 a release please can you try to indicate
> what
> > > you've checked. The reason for this is,  the tag Lewis has built off
> > isn't
> > > the tip of master, so if you're basing  your +1 on your day to day
> > > development and knowledge of the code base, that's not always whats
> > > shipped. Also in the branching process,  its possible merges or
> > alterations
> > > were accidentally made that Lewis has missed (this is very unlikely I
> > know
> > > but you know, code changes). Also people build software on different
> > OS's,
> > > versions of OS's etc so just because it builds on  Lewis's laptop
> doesn't
> > > mean it builds on mine, for example.
> > >
> > > Also regarding licenses, disclaimers etc, people notice different
> things
> > or
> > > interpret stuff differently. its always possible that someone might
> miss
> > a
> > > library etc so its important multiple eyes run over the same stuff.
> > >
> > > Cheers,
> > >
> > > Tom
> >
> > I'm hoping I'll have time to go through this tomorrow.
> >
> > matt
> >
> >
> >
> > > On Feb 25, 2017, at 2:41 AM, Tommaso Teofili <
> tommaso.teof...@gmail.com>
> > wrote:
> > >
> > > Hi Folks,
> > > Please VOTE on the Apache Joshua 6.1 Release Candidate #3.
> > >
> > > We solved 36 issues:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12319720=12335049
> > >
> > > Git source tag (3447715b3aa0a48ed79465d80618bd5a2f7a7558):
> > > https://s.apache.org/XIxJ
> > >
> > > Staging repo:
> > >
> https://repository.apache.org/content/repositories/orgapachejoshua-1004
> > >
> > > Source Release Artifacts:
> > > 

Re: [VOTE] Release Apache Joshua 6.1 (Incubating)

[kellen sunderland]

I have to -1 this release for the time being.  For me the signatures and
hashes don't seem to match the binaries downloaded.  Could you double check
that they match for you Tommaso?  I'm also getting a unit test that fails
when I run 'mvn clean package'.  I'm digging a little more into this one,
but suspect a missing file.



Here's what I've checked so far:

Release artifacts must include incubating in the final file name - YES
Release artifacts must include a disclaimer within the release artifact(s)
as noted - YES
Every ASF release MUST contain one or more source packages, which MUST be
sufficient for a user to build and test the release provided they have
access to the appropriate platform and tools. - NO
-Not building due to failing test (BerkleyLM failure).  I'm digging a
bit more into this.

Every artifact distributed to the public through Apache channels MUST be
accompanied by one file containing an OpenPGP compatible ASCII armored
detached signature and another file containing an MD5 checksum.
- .asc - NO
I get warning:
"gpg --verify joshua-incubating-6.1-src.tar.gz.asc
joshua-incubating-6.1-src.tar.gz
gpg: Signature made Thu Feb 23 09:15:17 2017 CET using RSA key ID
891768A5
gpg: Good signature from "Tommaso Teofili "
[unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the
owner."
- .md5 - NO
My md5 of joshua-incubating-6.1-src.tar.gz is
504976876b01294811293aa45b5400f5, the joshua-incubating-6.1-src.tar.gz.md5
indicates it should be 22b738eeae45757715080702a5bd2789
- .sha - NO
My sha of joshua-incubating-6.1-src.tar.gz is
4AB5BA24301590F36AE6452DACC3F21CBD8B3FEC, the
joshua-incubating-6.1-src.tar.gz.md5 indicates it should be
2a55b6d341dddc5369b22a4802a86ec40accd0a1
- KEYS - YES

On Mon, Feb 27, 2017 at 3:55 AM, Matt Post  wrote:

> Hi folks,
>
> First, Tommaso, thank you for pulling this together!
>
> I want to remind everyone that there's a checklist to go through before
> sending your +1. Here's from an email from Tom Barber a while back:
>
> > Hello folks,
> >
> > I see plenty of +1's going through the release vote,  which is great to
> see
> > people taking an active role in getting the release shipped.
> >
> > For those of you who are new to the ASF there are a bunch of requirements
> > to sign off for a release which you can find here:
> >
> > http://incubator.apache.org/guides/releasemanagement.html#check-list <
> http://incubator.apache.org/guides/releasemanagement.html#check-list>
> >
> > My current concern is that people who are new to the incubator are +1'ing
> > software for release without check all or part of the release cycle.
> Whilst
> > not mandatory, when you +1 a release please can you try to indicate what
> > you've checked. The reason for this is,  the tag Lewis has built off
> isn't
> > the tip of master, so if you're basing  your +1 on your day to day
> > development and knowledge of the code base, that's not always whats
> > shipped. Also in the branching process,  its possible merges or
> alterations
> > were accidentally made that Lewis has missed (this is very unlikely I
> know
> > but you know, code changes). Also people build software on different
> OS's,
> > versions of OS's etc so just because it builds on  Lewis's laptop doesn't
> > mean it builds on mine, for example.
> >
> > Also regarding licenses, disclaimers etc, people notice different things
> or
> > interpret stuff differently. its always possible that someone might miss
> a
> > library etc so its important multiple eyes run over the same stuff.
> >
> > Cheers,
> >
> > Tom
>
> I'm hoping I'll have time to go through this tomorrow.
>
> matt
>
>
>
> > On Feb 25, 2017, at 2:41 AM, Tommaso Teofili 
> wrote:
> >
> > Hi Folks,
> > Please VOTE on the Apache Joshua 6.1 Release Candidate #3.
> >
> > We solved 36 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12319720=12335049
> >
> > Git source tag (3447715b3aa0a48ed79465d80618bd5a2f7a7558):
> > https://s.apache.org/XIxJ
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/orgapachejoshua-1004
> >
> > Source Release Artifacts:
> > https://dist.apache.org/repos/dist/dev/incubator/joshua/6.1/
> >
> > PGP release keys (signed using 891768A5):
> > *https://git1-us-west.apache.org/repos/asf?p=incubator-
> joshua.git;a=blob_plain;f=KEYS;h=aa18365bf5c8c8fb17b084f783a75c
> 3a2460a98d;hb=HEAD
> >  joshua.git;a=blob_plain;f=KEYS;h=aa18365bf5c8c8fb17b084f783a75c
> 3a2460a98d;hb=HEAD>*
> >
> > Vote will be open for 72 hours.
> > Thank you to everyone that is able to VOTE as well as everyone that
> > contributed to Apache Joshua 6.1.
> >
> > [ ] +1, let's get it released!!!
> > [ ] +/-0, fine, but consider to fix few issues before...
> 

Re: [VOTE] Release Apache Joshua 6.1 (Incubating)

[Matt Post]

Hi folks,

First, Tommaso, thank you for pulling this together!

I want to remind everyone that there's a checklist to go through before sending 
your +1. Here's from an email from Tom Barber a while back:

> Hello folks,
> 
> I see plenty of +1's going through the release vote,  which is great to see
> people taking an active role in getting the release shipped.
> 
> For those of you who are new to the ASF there are a bunch of requirements
> to sign off for a release which you can find here:
> 
> http://incubator.apache.org/guides/releasemanagement.html#check-list 
> 
> 
> My current concern is that people who are new to the incubator are +1'ing
> software for release without check all or part of the release cycle. Whilst
> not mandatory, when you +1 a release please can you try to indicate what
> you've checked. The reason for this is,  the tag Lewis has built off isn't
> the tip of master, so if you're basing  your +1 on your day to day
> development and knowledge of the code base, that's not always whats
> shipped. Also in the branching process,  its possible merges or alterations
> were accidentally made that Lewis has missed (this is very unlikely I know
> but you know, code changes). Also people build software on different OS's,
> versions of OS's etc so just because it builds on  Lewis's laptop doesn't
> mean it builds on mine, for example.
> 
> Also regarding licenses, disclaimers etc, people notice different things or
> interpret stuff differently. its always possible that someone might miss a
> library etc so its important multiple eyes run over the same stuff.
> 
> Cheers,
> 
> Tom

I'm hoping I'll have time to go through this tomorrow.

matt



> On Feb 25, 2017, at 2:41 AM, Tommaso Teofili  
> wrote:
> 
> Hi Folks,
> Please VOTE on the Apache Joshua 6.1 Release Candidate #3.
> 
> We solved 36 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319720=12335049
> 
> Git source tag (3447715b3aa0a48ed79465d80618bd5a2f7a7558):
> https://s.apache.org/XIxJ
> 
> Staging repo:
> https://repository.apache.org/content/repositories/orgapachejoshua-1004
> 
> Source Release Artifacts:
> https://dist.apache.org/repos/dist/dev/incubator/joshua/6.1/
> 
> PGP release keys (signed using 891768A5):
> *https://git1-us-west.apache.org/repos/asf?p=incubator-joshua.git;a=blob_plain;f=KEYS;h=aa18365bf5c8c8fb17b084f783a75c3a2460a98d;hb=HEAD
> *
> 
> Vote will be open for 72 hours.
> Thank you to everyone that is able to VOTE as well as everyone that
> contributed to Apache Joshua 6.1.
> 
> [ ] +1, let's get it released!!!
> [ ] +/-0, fine, but consider to fix few issues before...
> [ ] -1, nope, because... (and please explain why)
> 
> Regards,
> Tommaso

[VOTE] Release Apache Joshua 6.1 (Incubating)

[Tommaso Teofili]

Hi Folks,
Please VOTE on the Apache Joshua 6.1 Release Candidate #3.

We solved 36 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319720=12335049

Git source tag (3447715b3aa0a48ed79465d80618bd5a2f7a7558):
https://s.apache.org/XIxJ

Staging repo:
https://repository.apache.org/content/repositories/orgapachejoshua-1004

Source Release Artifacts:
https://dist.apache.org/repos/dist/dev/incubator/joshua/6.1/

PGP release keys (signed using 891768A5):
*https://git1-us-west.apache.org/repos/asf?p=incubator-joshua.git;a=blob_plain;f=KEYS;h=aa18365bf5c8c8fb17b084f783a75c3a2460a98d;hb=HEAD
*

Vote will be open for 72 hours.
Thank you to everyone that is able to VOTE as well as everyone that
contributed to Apache Joshua 6.1.

[ ] +1, let's get it released!!!
[ ] +/-0, fine, but consider to fix few issues before...
[ ] -1, nope, because... (and please explain why)

Regards,
Tommaso