[VOTE] Release Groovy UNO Extension 0.1.4-RC2
This is for a source release of Groovy UNO Extension 0.1.4 from Apache OpenOffice and binaries made available from Maven via Apache Nexus. Source packages for RC2 are available at: https://dist.apache.org/repos/dist/dev/openoffice/devtools/ and the reference revision is r1740035. Binary Maven packages are staged here: https://repository.apache.org/content/repositories/orgapacheopenoffice-1019/ Please review the release testing instruction wiki page: https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing The [VOTE] will conclude no sooner than Monday 25 April, 14:00 UTC. Please do not do anything but [VOTE] (with any -1 explanation) on this thread. To discuss this vote or the process, please use a [DISCUSS][VOTE] reply rather than discussing on the [VOTE] thread. 3 binding +1 votes and a simple majority of votes are necessary for approval. So please VOTE on releasing RC2 (as defined above) as Groovy UNO Extension 0.1.4: [ ] +1 Approve [ ] 0 Abstain [ ] -1 Disapprove, with explanation Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4 - PLEASE VOTE
On 04/19/2016 06:29 PM, Patricia Shanahan wrote: On 4/19/2016 3:22 PM, Patricia Shanahan wrote: On 4/19/2016 4:20 AM, Carl Marcum wrote: On 04/18/2016 07:04 AM, Carl Marcum wrote: ... I have the most of what I wanted to add to the release testing page [1] done. If you would like to review and make any changes or additions feel free. :) I have added a process I devised for verifying that the test procedure really does test the locally built jar. I'm not sure that step is necessary for every PMC member intended to cast a binding +1 vote, but I did feel it should be done at least once. Now that we have a documented build and test procedure, I hope more PMC members will run the test and cast binding votes. The test procedure is described in https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing Thanks Patricia, It does no harm to make sure. I think I should create a new RC with the updated gradle.properties file included. I will post a new VOTE thread with the updated information. Thanks for the great help !! Regards, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4 - PLEASE VOTE
On 4/19/2016 3:22 PM, Patricia Shanahan wrote: On 4/19/2016 4:20 AM, Carl Marcum wrote: On 04/18/2016 07:04 AM, Carl Marcum wrote: ... I have the most of what I wanted to add to the release testing page [1] done. If you would like to review and make any changes or additions feel free. :) I have added a process I devised for verifying that the test procedure really does test the locally built jar. I'm not sure that step is necessary for every PMC member intended to cast a binding +1 vote, but I did feel it should be done at least once. Now that we have a documented build and test procedure, I hope more PMC members will run the test and cast binding votes. The test procedure is described in https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4
On 4/19/2016 4:20 AM, Carl Marcum wrote: On 04/18/2016 07:04 AM, Carl Marcum wrote: ... I have the most of what I wanted to add to the release testing page [1] done. If you would like to review and make any changes or additions feel free. :) I have added a process I devised for verifying that the test procedure really does test the locally built jar. I'm not sure that step is necessary for every PMC member intended to cast a binding +1 vote, but I did feel it should be done at least once. Now that we have a documented build and test procedure, I hope more PMC members will run the test and cast binding votes. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Completed Infrastructure Module
Moving onto the specialized modules now -Chris
Starting Infrastructure Module
Completed Introduction to Contributing to Apache OpenOffice Module
I've gotten myself registered on the recommended online services and have added my info to the volunteer directory. Chris
Re: [CWiki] Account Whitelisting
Chris Sirrs wrote: > Hello, > > My full name is Chris Sirrs. My username is Satyrane. > > Thanks > Chris; Your CWiki account Satyrane has been white-listed. Regards Keith N. McKenna signature.asc Description: OpenPGP digital signature
Re: [DISCUSS][VOTE] Release Groovy UNO Extension 0.1.4
On 04/18/2016 07:04 AM, Carl Marcum wrote: On 04/17/2016 08:48 PM, Patricia Shanahan wrote: On 4/17/2016 4:27 PM, Carl Marcum wrote: On 04/15/2016 10:01 PM, Patricia Shanahan wrote: On 4/15/2016 6:52 PM, Carl Marcum wrote: On 04/15/2016 09:21 PM, Patricia Shanahan wrote: ... Do I need to run it in any particular directory? How does it find the .jar I built? It doesn't need to find the jar you built. There is one pre-built from the RC and staged in Apache Nexus repository. ... I need to test the code I built before voting on the release. I think the intent is that each PMC member casting a binding +1 vote knows the supplied source code can be used to build a working version of the software. "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..." http://www.apache.org/dev/release.html#approving-a-release Hi Patricia, After going to Legal about this problem I got a great suggestion that requires running the test script once, thus downloading the staged release jar and setting up the local Groovy Ivy cache. Then build the test jar from the RC sources and replace the jar in the Ivy cache. Apologies in advance for the below instructions as I didn't have a lot of time this weekend. I should create a wiki page for this as it's kind of long. I'll try to work with these instructions, and go on asking questions whenever I get stuck. I have saved all the e-mails in this thread, and in any case they are in the archive. I think we should aim for a step-by-step Wiki page that may inspire another Windows-using PMC member to attempt the build and test. Hi Patricia, I have created a testing page [1] and a RC release prep page [2] and added links to the original page [3]. I can start on them this evening. [1] https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing [2] https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Preparation [3] https://wiki.openoffice.org/wiki/Groovy_UNO_Extension Thanks for your help !! Testing the guno-extension staged in Apache Nexus - Download the HelloTextTableShape.groovy test script from bugzilla If using Windows or a Linux with a soffice executable location other than "/opt/openoffice4/program/". Edit the test script for the location of the soffice executable. A Windows example would look like: "C:/Program Files (x86)/OpenOffice 4/program" Run the script from the download location groovy HelloTextTableShape.groovy The script should bootstrap the office and add sample content to some of the applications using the guno-extension jar. Close OpenOffice after the test. running the script should download the jars to the local Groovy Ivy cache On my Fedora Linux machine it is here: ~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.jar Testing the downloaded source --- unpack the source jar This will be the guno-extension test directory If using Windows or a Linux with a soffice executable location other than "/opt/openoffice4/program/". Edit the two Spock test files for the location of the soffice executable. src/test/groovy/org/openoffice/guno/SpreadsheetSpec.groovy and UnoSpec.groovy The default location is: String oooExeFolder = "/opt/openoffice4/program/" Do the test build. (From guno-extension test directory) gradle jar rename the downloaded jar in the local Groovy Ivy cache (From guno-extension test directory) mv ~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.jar ~/.groovy/grapes/org.openoffice/guno-extension/jars/guno-extension-0.1.4.save copy the test jar into it's place cp ./build/libs/guno-extension-0.1.4.jar ~/.groovy/grapes/org.openoffice/guno-extension/jars/ edit the HelloTextTableShape.groovy script and comment out the grab resolver for the staging area. This will make sure it can't see the staged jar. Groovy should find the newly built jar in the Ivy cache. // @GrabResolver(name = 'guno', root = 'https://repository.apache.org/content/repositories/orgapacheopenoffice-1019/') run the test script again to test the newly built jar. groovy HelloTextTableShape.groovy Once finished you can remove the test jar from Ivy and rename the guno-extension-0.1.4.save back to .jar Please let me know if you have any questions. Thanks, Carl Hi Patricia, I have the most of what I wanted to add to the release testing page [1] done. If you would like to review and make any changes or additions feel free. :) I can start on the release preparation page next. Thanks, Carl [1] https://wiki.openoffice.org/wiki/Groovy_Uno_Release_Testing - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[CWiki] Account Whitelisting
Hello, My full name is Chris Sirrs. My username is Satyrane. Thanks
Re: Reporting broken download link
Am 04/18/2016 12:15 PM, schrieb Antonietta Di renzo: salve ho un mac e ogni volta che tento di scaricare open office mi compare una scritta che mi dice che non è possibile installare il programma perché proveniente da uno sviluppatore non affidabile it looks like that the problem is the Gatekeeper function from Apple. Please see here [1] and [2] for more information how to solve the problem. Google translation: sembra che il problema è la funzione Gatekeeper da Apple. Si prega di consultare qui [1] e [2] per ulteriori informazioni su come risolvere il problema. [1] https://forum.openoffice.org/en/forum/viewtopic.php?f=17=80075=368517 [2] https://support.apple.com/en-us/HT202491 HTH Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Reporting broken download link
salve ho un mac e ogni volta che tento di scaricare open office mi compare una scritta che mi dice che non è possibile installare il programma perché proveniente da uno sviluppatore non affidabile - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
