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

2017-05-18 Thread 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

2017-05-03 Thread 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

2017-03-31 Thread 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

2017-03-20 Thread 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
>>> 
>>