Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
On Mon, 24 Jun 2019 18:57:30 +0100, Ian Dunlop wrote: > Hello > > I think I created a tagged rc2 in GitHub that I was going to use as the > basis for the release process. I also fixed most of the rc1 issues in it. I > think one of the problems was the name of the folders inside the file. I > was going to open the gz or zip, change the folder name and rezip it. Yes, then add pgp .asc signature and .sha256 / .sha512 checksum files. This is then uploaded to dist.apache.org with SVN, see our release procedure https://taverna.incubator.apache.org/community/releasing The above however assumes mvn which can do this as part of the release-plugin, but as Taverna Mobile is using Gradle we have to do the last part "manually" in the shell.. The RC to be voted on goes to https://dist.apache.org/repos/dist/dev/incubator/taverna/source/ (mark /dev/) while a release candidate under a folder name like incubator-taverna-mobile-1.0-incubating-RC2/ then if the vote is accepted (+3 votes by Taverna PMC, followed by +3 Incubator PMC votes while we are still a podling) .. then as the RC is accepted to become an official ASF release we do a SVN mv to https://dist.apache.org/repos/dist/release/incubator/taverna/source/ but without "-RC2" in the folder name, aka incubator-taverna-mobile-1.0-incubating This would then make its way to the official download mirrors and a day later we can update the download HTML page and send out email announcements. To avoid having to regenerate all those hashsum filenames and the PGP signature at thet svn mv time, then then the file itself should not have -RC2 in its name, and neither in its content, as it's a release candidate only for the purpose of the vote. Thus when testing during the vote, it will for all practical purposes claim to be 1.0-incubating. After the vote is passed we also re-tag the RC to the regular version number in git. On signing, see also https://www.apache.org/dev/release-signing.html
Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello I think I created a tagged rc2 in GitHub that I was going to use as the basis for the release process. I also fixed most of the rc1 issues in it. I think one of the problems was the name of the folders inside the file. I was going to open the gz or zip, change the folder name and rezip it. Cheers Ian On Wed, 12 Jun 2019, 05:36 Sagar, wrote: > Hi > > Could you guys share the guideline or step to create a release candidate. > So that I can fix the issues of the rc1 and create the new release > candidate. > > Thanks > > On Tue, Jun 11, 2019 at 11:29 PM Ian Dunlop wrote: > > > Hello > > > > Sorry I've been really busy and struggling for any time. I did fix the > > issues from rc1 and tagged an rc2 in the repo and I even started sorted > out > > the folder structure but then real life caught up and I didn't manage to > > get it out. Maybe someone could pick it up and run with it. > > > > Cheers > > > > Ian > > > > On Wed, 5 Jun 2019, 15:47 Stian Soiland-Reyes, wrote: > > > > > This went a bit tricky in the end.. so are we back to square 0 or can > we > > > try again for another RC2? It's not a blocker really if it says RC2 > > > inside the folder name.. just misleading. > > > (if the vote passes then 1.0.0-RC2 == 1.0.0) > > > > > > On Thu, 4 Apr 2019 14:01:58 +0100, Ian Dunlop > > > wrote: > > > > Hello, > > > > > > > > I think I know what you mean now. It’s the folder name inside the > > > .tar.gz when you explode it. Hmm. That seems to be be automatically put > > > together by GitHub based on the repo name and the tag name. Ie > > > incubator-taverna-mobile & 1.0-incubating-RC2. That’s slightly > annoying. > > > > So it looks like this GitHub release mechanism isn’t so great after > > > all. Or at least I’ll have to open the file and change the name then > gzip > > > it back up. Oh well. > > > > > > > > Cheers, > > > > > > > > Ian > > > > > > > > Sent from Mail for Windows 10 > > > > > > > > From: Ian Dunlop > > > > Sent: 04 April 2019 13:40 > > > > To: dev@taverna.incubator.apache.org > > > > Subject: RE: [DISCUSS] Release Apache Taverna Mobile > 1.0-incubating-RC1 > > > > > > > > Hello, > > > > > > > > @Stian I need a bit of clarification. Why did you say > > > > -1 "-RC1" in folder name inside (not ideal) > > > > > > > > Having RC1 in the folder name seems to agree with the instructions I > > > follow at > > > > > > https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg > > > > “Under source/, make a corresponding versioned folder for each > product, > > > and include the RC number, avoiding confusion in case you need to make > a > > > second release candidate:” > > > > > > > > Cheers, > > > > > > > > Ian > > > > > > > > > > > > Sent from Mail for Windows 10 > > > > > > > > From: Ian Dunlop > > > > Sent: 04 April 2019 13:19 > > > > To: Sagar > > > > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes > > > > Subject: RE: [DISCUSS] Release Apache Taverna Mobile > 1.0-incubating-RC1 > > > > > > > > Hello, > > > > > > > > Ok so I’m cancelling the current RC1 vote, merging the changes into > > > master and starting a vote on RC2. > > > > > > > > Cheers, > > > > > > > > Ian > > > > > > > > Sent from Mail for Windows 10 > > > > > > > > From: Sagar > > > > Sent: 03 April 2019 16:19 > > > > To: Ian Dunlop > > > > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes > > > > Subject: Re: [DISCUSS] Release Apache Taverna Mobile > 1.0-incubating-RC1 > > > > > > > > This looks good to me. > > > > > > > > On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop > > wrote: > > > > Hello, > > > > > > > > Adding the gradle download into the travis file appears to work. See > > > https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359 > . > > I > > > rolled the gradle changes back out of master and put them in branch > > > ian_travis_gradle. If everyone thinks this is an ok direction then we > can > > >
Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello Sorry I've been really busy and struggling for any time. I did fix the issues from rc1 and tagged an rc2 in the repo and I even started sorted out the folder structure but then real life caught up and I didn't manage to get it out. Maybe someone could pick it up and run with it. Cheers Ian On Wed, 5 Jun 2019, 15:47 Stian Soiland-Reyes, wrote: > This went a bit tricky in the end.. so are we back to square 0 or can we > try again for another RC2? It's not a blocker really if it says RC2 > inside the folder name.. just misleading. > (if the vote passes then 1.0.0-RC2 == 1.0.0) > > On Thu, 4 Apr 2019 14:01:58 +0100, Ian Dunlop > wrote: > > Hello, > > > > I think I know what you mean now. It’s the folder name inside the > .tar.gz when you explode it. Hmm. That seems to be be automatically put > together by GitHub based on the repo name and the tag name. Ie > incubator-taverna-mobile & 1.0-incubating-RC2. That’s slightly annoying. > > So it looks like this GitHub release mechanism isn’t so great after > all. Or at least I’ll have to open the file and change the name then gzip > it back up. Oh well. > > > > Cheers, > > > > Ian > > > > Sent from Mail for Windows 10 > > > > From: Ian Dunlop > > Sent: 04 April 2019 13:40 > > To: dev@taverna.incubator.apache.org > > Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > > > Hello, > > > > @Stian I need a bit of clarification. Why did you say > > -1 "-RC1" in folder name inside (not ideal) > > > > Having RC1 in the folder name seems to agree with the instructions I > follow at > https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg > > “Under source/, make a corresponding versioned folder for each product, > and include the RC number, avoiding confusion in case you need to make a > second release candidate:” > > > > Cheers, > > > > Ian > > > > > > Sent from Mail for Windows 10 > > > > From: Ian Dunlop > > Sent: 04 April 2019 13:19 > > To: Sagar > > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes > > Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > > > Hello, > > > > Ok so I’m cancelling the current RC1 vote, merging the changes into > master and starting a vote on RC2. > > > > Cheers, > > > > Ian > > > > Sent from Mail for Windows 10 > > > > From: Sagar > > Sent: 03 April 2019 16:19 > > To: Ian Dunlop > > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes > > Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > > > This looks good to me. > > > > On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop wrote: > > Hello, > > > > Adding the gradle download into the travis file appears to work. See > https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I > rolled the gradle changes back out of master and put them in branch > ian_travis_gradle. If everyone thinks this is an ok direction then we can > merge back into master and go for RC2 without the binary. > > > > Cheers, > > > > Ian > > > > Sent from Mail for Windows 10 > > > > From: Ian Dunlop > > Sent: 02 April 2019 18:10 > > To: Sagar > > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes > > Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > > > Hello > > > > The first answer on > https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907 > suggests > that you can get travis to create a gradle wrapper for you. We could try > that and see if it works. I'm just trying to make the process simple. For > Devs you only need to install gradle and run the gradle wrapper command > once and then you are all setup. I guess we could also write a shell script > to create the bundle for us. Open to all suggestions. > > Feel free to back out any of my changes if they are causing you problems > but we need to think of a solution. > > > > Cheers > > > > Ian > > > > On Tue, 2 Apr 2019, 18:00 Ian Dunlop, wrote: > > Hello > > > > That makes it a tricky problem to solve. If we can't rely on the GitHub > tag for the bundle then we will need to create our own after cloning and > removing the gradle folder. Can Travis create a gradle wrapper before > building? I'm happy to go with creating our own bundle but it is more work. > Remove git folder, remove gradle etc. > > > > Cheers > > > > Ian > &
RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
This went a bit tricky in the end.. so are we back to square 0 or can we try again for another RC2? It's not a blocker really if it says RC2 inside the folder name.. just misleading. (if the vote passes then 1.0.0-RC2 == 1.0.0) On Thu, 4 Apr 2019 14:01:58 +0100, Ian Dunlop wrote: > Hello, > > I think I know what you mean now. It’s the folder name inside the .tar.gz > when you explode it. Hmm. That seems to be be automatically put together by > GitHub based on the repo name and the tag name. Ie incubator-taverna-mobile & > 1.0-incubating-RC2. That’s slightly annoying. > So it looks like this GitHub release mechanism isn’t so great after all. Or > at least I’ll have to open the file and change the name then gzip it back up. > Oh well. > > Cheers, > > Ian > > Sent from Mail for Windows 10 > > From: Ian Dunlop > Sent: 04 April 2019 13:40 > To: dev@taverna.incubator.apache.org > Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > Hello, > > @Stian I need a bit of clarification. Why did you say > -1 "-RC1" in folder name inside (not ideal) > > Having RC1 in the folder name seems to agree with the instructions I follow > at > https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg > “Under source/, make a corresponding versioned folder for each product, and > include the RC number, avoiding confusion in case you need to make a second > release candidate:” > > Cheers, > > Ian > > > Sent from Mail for Windows 10 > > From: Ian Dunlop > Sent: 04 April 2019 13:19 > To: Sagar > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes > Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > Hello, > > Ok so I’m cancelling the current RC1 vote, merging the changes into master > and starting a vote on RC2. > > Cheers, > > Ian > > Sent from Mail for Windows 10 > > From: Sagar > Sent: 03 April 2019 16:19 > To: Ian Dunlop > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes > Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > This looks good to me. > > On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop wrote: > Hello, > > Adding the gradle download into the travis file appears to work. See > https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I > rolled the gradle changes back out of master and put them in branch > ian_travis_gradle. If everyone thinks this is an ok direction then we can > merge back into master and go for RC2 without the binary. > > Cheers, > > Ian > > Sent from Mail for Windows 10 > > From: Ian Dunlop > Sent: 02 April 2019 18:10 > To: Sagar > Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes > Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > Hello > > The first answer on > https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907 > suggests that you can get travis to create a gradle wrapper for you. We > could try that and see if it works. I'm just trying to make the process > simple. For Devs you only need to install gradle and run the gradle wrapper > command once and then you are all setup. I guess we could also write a shell > script to create the bundle for us. Open to all suggestions. > Feel free to back out any of my changes if they are causing you problems but > we need to think of a solution. > > Cheers > > Ian > > On Tue, 2 Apr 2019, 18:00 Ian Dunlop, wrote: > Hello > > That makes it a tricky problem to solve. If we can't rely on the GitHub tag > for the bundle then we will need to create our own after cloning and removing > the gradle folder. Can Travis create a gradle wrapper before building? I'm > happy to go with creating our own bundle but it is more work. Remove git > folder, remove gradle etc. > > Cheers > > Ian > > On Tue, 2 Apr 2019, 17:15 Sagar, wrote: > Due to removing the wrapper. We will not able to build the project. It is > required to build the android code. Travis is also failing because of this. > > On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop wrote: > Hello > > I just commited some fixes. Hopefully all the files have the correct headers > now. I also removed the gradle wrapper. Now you have to create the wrapper > yourself when you first clone the project. Seems like the easiest way to > avoid the binary issue. I think I've got the issues fixed so I can try and > put RC2 together soon. Hopefully my key issue is fixed as well. Maybe someone > could check for me. > > Cheers, > > Ian > &
RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello, I think I know what you mean now. It’s the folder name inside the .tar.gz when you explode it. Hmm. That seems to be be automatically put together by GitHub based on the repo name and the tag name. Ie incubator-taverna-mobile & 1.0-incubating-RC2. That’s slightly annoying. So it looks like this GitHub release mechanism isn’t so great after all. Or at least I’ll have to open the file and change the name then gzip it back up. Oh well. Cheers, Ian Sent from Mail for Windows 10 From: Ian Dunlop Sent: 04 April 2019 13:40 To: dev@taverna.incubator.apache.org Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 Hello, @Stian I need a bit of clarification. Why did you say -1 "-RC1" in folder name inside (not ideal) Having RC1 in the folder name seems to agree with the instructions I follow at https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg “Under source/, make a corresponding versioned folder for each product, and include the RC number, avoiding confusion in case you need to make a second release candidate:” Cheers, Ian Sent from Mail for Windows 10 From: Ian Dunlop Sent: 04 April 2019 13:19 To: Sagar Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 Hello, Ok so I’m cancelling the current RC1 vote, merging the changes into master and starting a vote on RC2. Cheers, Ian Sent from Mail for Windows 10 From: Sagar Sent: 03 April 2019 16:19 To: Ian Dunlop Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 This looks good to me. On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop wrote: Hello, Adding the gradle download into the travis file appears to work. See https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I rolled the gradle changes back out of master and put them in branch ian_travis_gradle. If everyone thinks this is an ok direction then we can merge back into master and go for RC2 without the binary. Cheers, Ian Sent from Mail for Windows 10 From: Ian Dunlop Sent: 02 April 2019 18:10 To: Sagar Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 Hello The first answer on https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907 suggests that you can get travis to create a gradle wrapper for you. We could try that and see if it works. I'm just trying to make the process simple. For Devs you only need to install gradle and run the gradle wrapper command once and then you are all setup. I guess we could also write a shell script to create the bundle for us. Open to all suggestions. Feel free to back out any of my changes if they are causing you problems but we need to think of a solution. Cheers Ian On Tue, 2 Apr 2019, 18:00 Ian Dunlop, wrote: Hello That makes it a tricky problem to solve. If we can't rely on the GitHub tag for the bundle then we will need to create our own after cloning and removing the gradle folder. Can Travis create a gradle wrapper before building? I'm happy to go with creating our own bundle but it is more work. Remove git folder, remove gradle etc. Cheers Ian On Tue, 2 Apr 2019, 17:15 Sagar, wrote: Due to removing the wrapper. We will not able to build the project. It is required to build the android code. Travis is also failing because of this. On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop wrote: Hello I just commited some fixes. Hopefully all the files have the correct headers now. I also removed the gradle wrapper. Now you have to create the wrapper yourself when you first clone the project. Seems like the easiest way to avoid the binary issue. I think I've got the issues fixed so I can try and put RC2 together soon. Hopefully my key issue is fixed as well. Maybe someone could check for me. Cheers, Ian On Tue, 2 Apr 2019, 15:10 Sagar, wrote: @Ian Dunlop Are you working on the issues or do I make the change? On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop wrote: Hello, The key fingerprint is the same as listed in the KEYS file. Does that mean the key is the same? Cheers, Ian Sent from Mail for Windows 10 From: Stian Soiland-Reyes Sent: 01 April 2019 16:43 To: Ian Dunlop Cc: dev@taverna.incubator.apache.org Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 You'll also need to update the KEYS file in dist. On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop wrote: > Hello, > > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it > passes all the Apache release criteria. I think I just posted my VOTE to the > DISCUSS thread – not sure message threading is working correctly in my email > client. Apologies for any confusion. > > I’ve updated my key on the keyservers
RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello, @Stian I need a bit of clarification. Why did you say -1 "-RC1" in folder name inside (not ideal) Having RC1 in the folder name seems to agree with the instructions I follow at https://taverna.incubator.apache.org/community/releasing#uploading-to-distapacheorg “Under source/, make a corresponding versioned folder for each product, and include the RC number, avoiding confusion in case you need to make a second release candidate:” Cheers, Ian Sent from Mail for Windows 10 From: Ian Dunlop Sent: 04 April 2019 13:19 To: Sagar Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 Hello, Ok so I’m cancelling the current RC1 vote, merging the changes into master and starting a vote on RC2. Cheers, Ian Sent from Mail for Windows 10 From: Sagar Sent: 03 April 2019 16:19 To: Ian Dunlop Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 This looks good to me. On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop wrote: Hello, Adding the gradle download into the travis file appears to work. See https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I rolled the gradle changes back out of master and put them in branch ian_travis_gradle. If everyone thinks this is an ok direction then we can merge back into master and go for RC2 without the binary. Cheers, Ian Sent from Mail for Windows 10 From: Ian Dunlop Sent: 02 April 2019 18:10 To: Sagar Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 Hello The first answer on https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907 suggests that you can get travis to create a gradle wrapper for you. We could try that and see if it works. I'm just trying to make the process simple. For Devs you only need to install gradle and run the gradle wrapper command once and then you are all setup. I guess we could also write a shell script to create the bundle for us. Open to all suggestions. Feel free to back out any of my changes if they are causing you problems but we need to think of a solution. Cheers Ian On Tue, 2 Apr 2019, 18:00 Ian Dunlop, wrote: Hello That makes it a tricky problem to solve. If we can't rely on the GitHub tag for the bundle then we will need to create our own after cloning and removing the gradle folder. Can Travis create a gradle wrapper before building? I'm happy to go with creating our own bundle but it is more work. Remove git folder, remove gradle etc. Cheers Ian On Tue, 2 Apr 2019, 17:15 Sagar, wrote: Due to removing the wrapper. We will not able to build the project. It is required to build the android code. Travis is also failing because of this. On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop wrote: Hello I just commited some fixes. Hopefully all the files have the correct headers now. I also removed the gradle wrapper. Now you have to create the wrapper yourself when you first clone the project. Seems like the easiest way to avoid the binary issue. I think I've got the issues fixed so I can try and put RC2 together soon. Hopefully my key issue is fixed as well. Maybe someone could check for me. Cheers, Ian On Tue, 2 Apr 2019, 15:10 Sagar, wrote: @Ian Dunlop Are you working on the issues or do I make the change? On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop wrote: Hello, The key fingerprint is the same as listed in the KEYS file. Does that mean the key is the same? Cheers, Ian Sent from Mail for Windows 10 From: Stian Soiland-Reyes Sent: 01 April 2019 16:43 To: Ian Dunlop Cc: dev@taverna.incubator.apache.org Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 You'll also need to update the KEYS file in dist. On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop wrote: > Hello, > > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it > passes all the Apache release criteria. I think I just posted my VOTE to the > DISCUSS thread – not sure message threading is working correctly in my email > client. Apologies for any confusion. > > I’ve updated my key on the keyservers (gpg & ubuntu though they should both > sync anyway). Let’s see if that fixes things because I’m sure I’ve updated > them before. > I guess we should give them 24 hours to sort themselves out and then gpg > --refresh-keys to update your local keys. -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd. -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd. -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd.
RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello, Ok so I’m cancelling the current RC1 vote, merging the changes into master and starting a vote on RC2. Cheers, Ian Sent from Mail for Windows 10 From: Sagar Sent: 03 April 2019 16:19 To: Ian Dunlop Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 This looks good to me. On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop wrote: Hello, Adding the gradle download into the travis file appears to work. See https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I rolled the gradle changes back out of master and put them in branch ian_travis_gradle. If everyone thinks this is an ok direction then we can merge back into master and go for RC2 without the binary. Cheers, Ian Sent from Mail for Windows 10 From: Ian Dunlop Sent: 02 April 2019 18:10 To: Sagar Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 Hello The first answer on https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907 suggests that you can get travis to create a gradle wrapper for you. We could try that and see if it works. I'm just trying to make the process simple. For Devs you only need to install gradle and run the gradle wrapper command once and then you are all setup. I guess we could also write a shell script to create the bundle for us. Open to all suggestions. Feel free to back out any of my changes if they are causing you problems but we need to think of a solution. Cheers Ian On Tue, 2 Apr 2019, 18:00 Ian Dunlop, wrote: Hello That makes it a tricky problem to solve. If we can't rely on the GitHub tag for the bundle then we will need to create our own after cloning and removing the gradle folder. Can Travis create a gradle wrapper before building? I'm happy to go with creating our own bundle but it is more work. Remove git folder, remove gradle etc. Cheers Ian On Tue, 2 Apr 2019, 17:15 Sagar, wrote: Due to removing the wrapper. We will not able to build the project. It is required to build the android code. Travis is also failing because of this. On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop wrote: Hello I just commited some fixes. Hopefully all the files have the correct headers now. I also removed the gradle wrapper. Now you have to create the wrapper yourself when you first clone the project. Seems like the easiest way to avoid the binary issue. I think I've got the issues fixed so I can try and put RC2 together soon. Hopefully my key issue is fixed as well. Maybe someone could check for me. Cheers, Ian On Tue, 2 Apr 2019, 15:10 Sagar, wrote: @Ian Dunlop Are you working on the issues or do I make the change? On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop wrote: Hello, The key fingerprint is the same as listed in the KEYS file. Does that mean the key is the same? Cheers, Ian Sent from Mail for Windows 10 From: Stian Soiland-Reyes Sent: 01 April 2019 16:43 To: Ian Dunlop Cc: dev@taverna.incubator.apache.org Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 You'll also need to update the KEYS file in dist. On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop wrote: > Hello, > > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it > passes all the Apache release criteria. I think I just posted my VOTE to the > DISCUSS thread – not sure message threading is working correctly in my email > client. Apologies for any confusion. > > I’ve updated my key on the keyservers (gpg & ubuntu though they should both > sync anyway). Let’s see if that fixes things because I’m sure I’ve updated > them before. > I guess we should give them 24 hours to sort themselves out and then gpg > --refresh-keys to update your local keys. -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd. -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd. -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd.
Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
This looks good to me. On Wed, Apr 3, 2019 at 4:00 PM Ian Dunlop wrote: > Hello, > > > > Adding the gradle download into the travis file appears to work. See > https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I > rolled the gradle changes back out of master and put them in branch > ian_travis_gradle. If everyone thinks this is an ok direction then we can > merge back into master and go for RC2 without the binary. > > > > Cheers, > > > > Ian > > > > Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for > Windows 10 > > > > *From: *Ian Dunlop > *Sent: *02 April 2019 18:10 > *To: *Sagar > *Cc: *dev@taverna.incubator.apache.org; Stian Soiland-Reyes > > *Subject: *Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > > > Hello > > > > The first answer on > https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907 > suggests > that you can get travis to create a gradle wrapper for you. We could try > that and see if it works. I'm just trying to make the process simple. For > Devs you only need to install gradle and run the gradle wrapper command > once and then you are all setup. I guess we could also write a shell script > to create the bundle for us. Open to all suggestions. > > Feel free to back out any of my changes if they are causing you problems > but we need to think of a solution. > > > > Cheers > > > > Ian > > > > On Tue, 2 Apr 2019, 18:00 Ian Dunlop, wrote: > > Hello > > > > That makes it a tricky problem to solve. If we can't rely on the GitHub > tag for the bundle then we will need to create our own after cloning and > removing the gradle folder. Can Travis create a gradle wrapper before > building? I'm happy to go with creating our own bundle but it is more work. > Remove git folder, remove gradle etc. > > > > Cheers > > > > Ian > > > > On Tue, 2 Apr 2019, 17:15 Sagar, wrote: > > Due to removing the wrapper. We will not able to build the project. It is > required to build the android code. Travis is also failing because of this. > > > > On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop wrote: > > Hello > > > > I just commited some fixes. Hopefully all the files have the correct > headers now. I also removed the gradle wrapper. Now you have to create the > wrapper yourself when you first clone the project. Seems like the easiest > way to avoid the binary issue. I think I've got the issues fixed so I can > try and put RC2 together soon. Hopefully my key issue is fixed as well. > Maybe someone could check for me. > > > > Cheers, > > > > Ian > > > > On Tue, 2 Apr 2019, 15:10 Sagar, wrote: > > @Ian Dunlop Are you working on the issues or do I > make the change? > > > > > > > > On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop wrote: > > Hello, > > The key fingerprint is the same as listed in the KEYS file. Does that mean > the key is the same? > > Cheers, > > Ian > > Sent from Mail for Windows 10 > > From: Stian Soiland-Reyes > Sent: 01 April 2019 16:43 > To: Ian Dunlop > Cc: dev@taverna.incubator.apache.org > Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > You'll also need to update the KEYS file in dist. > > On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop > wrote: > > Hello, > > > > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it > passes all the Apache release criteria. I think I just posted my VOTE to > the DISCUSS thread – not sure message threading is working correctly in my > email client. Apologies for any confusion. > > > > I’ve updated my key on the keyservers (gpg & ubuntu though they should > both sync anyway). Let’s see if that fixes things because I’m sure I’ve > updated them before. > > I guess we should give them 24 hours to sort themselves out and then gpg > --refresh-keys to update your local keys. > > > > > -- > > > > Warmest regards > > Sagar > > Software Developer > > Lattice Innovations Pvt. Ltd. > > > > > -- > > > > Warmest regards > > Sagar > > Software Developer > > Lattice Innovations Pvt. Ltd. > > > -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd.
RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello, Adding the gradle download into the travis file appears to work. See https://travis-ci.org/apache/incubator-taverna-mobile/builds/515120359. I rolled the gradle changes back out of master and put them in branch ian_travis_gradle. If everyone thinks this is an ok direction then we can merge back into master and go for RC2 without the binary. Cheers, Ian Sent from Mail for Windows 10 From: Ian Dunlop Sent: 02 April 2019 18:10 To: Sagar Cc: dev@taverna.incubator.apache.org; Stian Soiland-Reyes Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 Hello The first answer on https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907 suggests that you can get travis to create a gradle wrapper for you. We could try that and see if it works. I'm just trying to make the process simple. For Devs you only need to install gradle and run the gradle wrapper command once and then you are all setup. I guess we could also write a shell script to create the bundle for us. Open to all suggestions. Feel free to back out any of my changes if they are causing you problems but we need to think of a solution. Cheers Ian On Tue, 2 Apr 2019, 18:00 Ian Dunlop, wrote: Hello That makes it a tricky problem to solve. If we can't rely on the GitHub tag for the bundle then we will need to create our own after cloning and removing the gradle folder. Can Travis create a gradle wrapper before building? I'm happy to go with creating our own bundle but it is more work. Remove git folder, remove gradle etc. Cheers Ian On Tue, 2 Apr 2019, 17:15 Sagar, wrote: Due to removing the wrapper. We will not able to build the project. It is required to build the android code. Travis is also failing because of this. On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop wrote: Hello I just commited some fixes. Hopefully all the files have the correct headers now. I also removed the gradle wrapper. Now you have to create the wrapper yourself when you first clone the project. Seems like the easiest way to avoid the binary issue. I think I've got the issues fixed so I can try and put RC2 together soon. Hopefully my key issue is fixed as well. Maybe someone could check for me. Cheers, Ian On Tue, 2 Apr 2019, 15:10 Sagar, wrote: @Ian Dunlop Are you working on the issues or do I make the change? On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop wrote: Hello, The key fingerprint is the same as listed in the KEYS file. Does that mean the key is the same? Cheers, Ian Sent from Mail for Windows 10 From: Stian Soiland-Reyes Sent: 01 April 2019 16:43 To: Ian Dunlop Cc: dev@taverna.incubator.apache.org Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 You'll also need to update the KEYS file in dist. On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop wrote: > Hello, > > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it > passes all the Apache release criteria. I think I just posted my VOTE to the > DISCUSS thread – not sure message threading is working correctly in my email > client. Apologies for any confusion. > > I’ve updated my key on the keyservers (gpg & ubuntu though they should both > sync anyway). Let’s see if that fixes things because I’m sure I’ve updated > them before. > I guess we should give them 24 hours to sort themselves out and then gpg > --refresh-keys to update your local keys. -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd. -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd.
Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello The first answer on https://stackoverflow.com/questions/42818269/is-gradlew-mandatory-for-travis-ci-to-work/43493907 suggests that you can get travis to create a gradle wrapper for you. We could try that and see if it works. I'm just trying to make the process simple. For Devs you only need to install gradle and run the gradle wrapper command once and then you are all setup. I guess we could also write a shell script to create the bundle for us. Open to all suggestions. Feel free to back out any of my changes if they are causing you problems but we need to think of a solution. Cheers Ian On Tue, 2 Apr 2019, 18:00 Ian Dunlop, wrote: > Hello > > That makes it a tricky problem to solve. If we can't rely on the GitHub > tag for the bundle then we will need to create our own after cloning and > removing the gradle folder. Can Travis create a gradle wrapper before > building? I'm happy to go with creating our own bundle but it is more work. > Remove git folder, remove gradle etc. > > Cheers > > Ian > > On Tue, 2 Apr 2019, 17:15 Sagar, wrote: > >> Due to removing the wrapper. We will not able to build the project. It is >> required to build the android code. Travis is also failing because of this. >> >> >> >> On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop wrote: >> >>> Hello >>> >>> I just commited some fixes. Hopefully all the files have the correct >>> headers now. I also removed the gradle wrapper. Now you have to create the >>> wrapper yourself when you first clone the project. Seems like the easiest >>> way to avoid the binary issue. I think I've got the issues fixed so I can >>> try and put RC2 together soon. Hopefully my key issue is fixed as well. >>> Maybe someone could check for me. >>> >>> Cheers, >>> >>> Ian >>> >>> On Tue, 2 Apr 2019, 15:10 Sagar, wrote: >>> >>>> @Ian Dunlop Are you working on the issues or >>>> do I make the change? >>>> >>>> >>>> >>>> >>>> >>>> On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop wrote: >>>> >>>>> Hello, >>>>> >>>>> The key fingerprint is the same as listed in the KEYS file. Does that >>>>> mean the key is the same? >>>>> >>>>> Cheers, >>>>> >>>>> Ian >>>>> >>>>> Sent from Mail for Windows 10 >>>>> >>>>> From: Stian Soiland-Reyes >>>>> Sent: 01 April 2019 16:43 >>>>> To: Ian Dunlop >>>>> Cc: dev@taverna.incubator.apache.org >>>>> Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 >>>>> >>>>> You'll also need to update the KEYS file in dist. >>>>> >>>>> On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop >>>>> wrote: >>>>> > Hello, >>>>> > >>>>> > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you >>>>> think it passes all the Apache release criteria. I think I just posted my >>>>> VOTE to the DISCUSS thread – not sure message threading is working >>>>> correctly in my email client. Apologies for any confusion. >>>>> > >>>>> > I’ve updated my key on the keyservers (gpg & ubuntu though they >>>>> should both sync anyway). Let’s see if that fixes things because I’m sure >>>>> I’ve updated them before. >>>>> > I guess we should give them 24 hours to sort themselves out and then >>>>> gpg --refresh-keys to update your local keys. >>>>> >>>>> >>>> >>>> -- >>>> >>>> Warmest regards >>>> Sagar >>>> Software Developer >>>> Lattice Innovations Pvt. Ltd. >>>> >>> >> >> -- >> >> Warmest regards >> Sagar >> Software Developer >> Lattice Innovations Pvt. Ltd. >> >
Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello That makes it a tricky problem to solve. If we can't rely on the GitHub tag for the bundle then we will need to create our own after cloning and removing the gradle folder. Can Travis create a gradle wrapper before building? I'm happy to go with creating our own bundle but it is more work. Remove git folder, remove gradle etc. Cheers Ian On Tue, 2 Apr 2019, 17:15 Sagar, wrote: > Due to removing the wrapper. We will not able to build the project. It is > required to build the android code. Travis is also failing because of this. > > > > On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop wrote: > >> Hello >> >> I just commited some fixes. Hopefully all the files have the correct >> headers now. I also removed the gradle wrapper. Now you have to create the >> wrapper yourself when you first clone the project. Seems like the easiest >> way to avoid the binary issue. I think I've got the issues fixed so I can >> try and put RC2 together soon. Hopefully my key issue is fixed as well. >> Maybe someone could check for me. >> >> Cheers, >> >> Ian >> >> On Tue, 2 Apr 2019, 15:10 Sagar, wrote: >> >>> @Ian Dunlop Are you working on the issues or do >>> I make the change? >>> >>> >>> >>> >>> >>> On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop wrote: >>> >>>> Hello, >>>> >>>> The key fingerprint is the same as listed in the KEYS file. Does that >>>> mean the key is the same? >>>> >>>> Cheers, >>>> >>>> Ian >>>> >>>> Sent from Mail for Windows 10 >>>> >>>> From: Stian Soiland-Reyes >>>> Sent: 01 April 2019 16:43 >>>> To: Ian Dunlop >>>> Cc: dev@taverna.incubator.apache.org >>>> Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 >>>> >>>> You'll also need to update the KEYS file in dist. >>>> >>>> On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop >>>> wrote: >>>> > Hello, >>>> > >>>> > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think >>>> it passes all the Apache release criteria. I think I just posted my VOTE to >>>> the DISCUSS thread – not sure message threading is working correctly in my >>>> email client. Apologies for any confusion. >>>> > >>>> > I’ve updated my key on the keyservers (gpg & ubuntu though they >>>> should both sync anyway). Let’s see if that fixes things because I’m sure >>>> I’ve updated them before. >>>> > I guess we should give them 24 hours to sort themselves out and then >>>> gpg --refresh-keys to update your local keys. >>>> >>>> >>> >>> -- >>> >>> Warmest regards >>> Sagar >>> Software Developer >>> Lattice Innovations Pvt. Ltd. >>> >> > > -- > > Warmest regards > Sagar > Software Developer > Lattice Innovations Pvt. Ltd. >
Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Due to removing the wrapper. We will not able to build the project. It is required to build the android code. Travis is also failing because of this. On Tue, Apr 2, 2019 at 8:53 PM Ian Dunlop wrote: > Hello > > I just commited some fixes. Hopefully all the files have the correct > headers now. I also removed the gradle wrapper. Now you have to create the > wrapper yourself when you first clone the project. Seems like the easiest > way to avoid the binary issue. I think I've got the issues fixed so I can > try and put RC2 together soon. Hopefully my key issue is fixed as well. > Maybe someone could check for me. > > Cheers, > > Ian > > On Tue, 2 Apr 2019, 15:10 Sagar, wrote: > >> @Ian Dunlop Are you working on the issues or do >> I make the change? >> >> >> >> >> >> On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop wrote: >> >>> Hello, >>> >>> The key fingerprint is the same as listed in the KEYS file. Does that >>> mean the key is the same? >>> >>> Cheers, >>> >>> Ian >>> >>> Sent from Mail for Windows 10 >>> >>> From: Stian Soiland-Reyes >>> Sent: 01 April 2019 16:43 >>> To: Ian Dunlop >>> Cc: dev@taverna.incubator.apache.org >>> Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 >>> >>> You'll also need to update the KEYS file in dist. >>> >>> On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop >>> wrote: >>> > Hello, >>> > >>> > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think >>> it passes all the Apache release criteria. I think I just posted my VOTE to >>> the DISCUSS thread – not sure message threading is working correctly in my >>> email client. Apologies for any confusion. >>> > >>> > I’ve updated my key on the keyservers (gpg & ubuntu though they should >>> both sync anyway). Let’s see if that fixes things because I’m sure I’ve >>> updated them before. >>> > I guess we should give them 24 hours to sort themselves out and then >>> gpg --refresh-keys to update your local keys. >>> >>> >> >> -- >> >> Warmest regards >> Sagar >> Software Developer >> Lattice Innovations Pvt. Ltd. >> > -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd.
Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
@Ian Dunlop Are you working on the issues or do I make the change? On Mon, Apr 1, 2019 at 9:41 PM Ian Dunlop wrote: > Hello, > > The key fingerprint is the same as listed in the KEYS file. Does that mean > the key is the same? > > Cheers, > > Ian > > Sent from Mail for Windows 10 > > From: Stian Soiland-Reyes > Sent: 01 April 2019 16:43 > To: Ian Dunlop > Cc: dev@taverna.incubator.apache.org > Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 > > You'll also need to update the KEYS file in dist. > > On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop > wrote: > > Hello, > > > > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it > passes all the Apache release criteria. I think I just posted my VOTE to > the DISCUSS thread – not sure message threading is working correctly in my > email client. Apologies for any confusion. > > > > I’ve updated my key on the keyservers (gpg & ubuntu though they should > both sync anyway). Let’s see if that fixes things because I’m sure I’ve > updated them before. > > I guess we should give them 24 hours to sort themselves out and then gpg > --refresh-keys to update your local keys. > > -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd.
RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello, The key fingerprint is the same as listed in the KEYS file. Does that mean the key is the same? Cheers, Ian Sent from Mail for Windows 10 From: Stian Soiland-Reyes Sent: 01 April 2019 16:43 To: Ian Dunlop Cc: dev@taverna.incubator.apache.org Subject: RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 You'll also need to update the KEYS file in dist. On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop wrote: > Hello, > > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it > passes all the Apache release criteria. I think I just posted my VOTE to the > DISCUSS thread – not sure message threading is working correctly in my email > client. Apologies for any confusion. > > I’ve updated my key on the keyservers (gpg & ubuntu though they should both > sync anyway). Let’s see if that fixes things because I’m sure I’ve updated > them before. > I guess we should give them 24 hours to sort themselves out and then gpg > --refresh-keys to update your local keys.
Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
On Fri, 29 Mar 2019 19:38:28 +, Ian Dunlop wrote: > Please discuss the release of Apache Taverna Mobile 1.0-incubating-RC1 in > this thread. As I mentioned in my VOTE there were some files missing ASF headers. If these files are not made by us then they will need to be removed/replaced or get their appropriate license/attribution forwarded on from their source. https://paste.apache.org/EUQI I don't think we should include gradle.jar in the download, as this is meant to be a source distribution. Why is it needed in the repository? -- Stian Soiland-Reyes The University of Manchester https://www.esciencelab.org.uk/ https://orcid.org/-0001-9842-9718
RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
You'll also need to update the KEYS file in dist. On Mon, 1 Apr 2019 13:39:40 +0100, Ian Dunlop wrote: > Hello, > > @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it > passes all the Apache release criteria. I think I just posted my VOTE to the > DISCUSS thread – not sure message threading is working correctly in my email > client. Apologies for any confusion. > > I’ve updated my key on the keyservers (gpg & ubuntu though they should both > sync anyway). Let’s see if that fixes things because I’m sure I’ve updated > them before. > I guess we should give them 24 hours to sort themselves out and then gpg > --refresh-keys to update your local keys.
RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello, @Sagar don’t forget to give it a +1 on the [VOTE] thread if you think it passes all the Apache release criteria. I think I just posted my VOTE to the DISCUSS thread – not sure message threading is working correctly in my email client. Apologies for any confusion. I’ve updated my key on the keyservers (gpg & ubuntu though they should both sync anyway). Let’s see if that fixes things because I’m sure I’ve updated them before. I guess we should give them 24 hours to sort themselves out and then gpg --refresh-keys to update your local keys. Cheers, Sent from Mail for Windows 10 From: Ian Dunlop Sent: 29 March 2019 19:41 To: dev@taverna.incubator.apache.org Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 Hello, Sagar noted that the gpg key I used to sign the release had expired. I need to double check this and update it in the keyservers if necessary. I'm not sure whether it matters or not for the purposes of checking the release but something to fix for next time. Cheers, Ian On Fri, 29 Mar 2019, 19:38 Ian Dunlop, wrote: Hello, Please discuss the release of Apache Taverna Mobile 1.0-incubating-RC1 in this thread. Cheers, Ian
RE: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello, Built successfully on ubuntu 16.04. SHA1 & MD5 checksums match. GPG signed .tar.gz source bundle verified. Licence, NOTICE, apache file headers all good. +1 Cheers, Ian Sent from Mail for Windows 10 From: Sagar Sent: 29 March 2019 12:42 To: dev@taverna.incubator.apache.org Subject: Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1 Built successfully. md5 & sha1 checksums all match and also verified the GPG keys but your key has expired. does it make any issue? On Thu, Mar 28, 2019 at 9:53 PM Ian Dunlop wrote: > Hello, > > Please discuss the release of Apache Taverna Mobile 1.0-incubating-RC1 in > this thread. > > Cheers, > > Ian > > Sent from Mail for Windows 10 > > -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd.
Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Hello, Sagar noted that the gpg key I used to sign the release had expired. I need to double check this and update it in the keyservers if necessary. I'm not sure whether it matters or not for the purposes of checking the release but something to fix for next time. Cheers, Ian On Fri, 29 Mar 2019, 19:38 Ian Dunlop, wrote: > Hello, > > Please discuss the release of Apache Taverna Mobile 1.0-incubating-RC1 in > this thread. > > Cheers, > > Ian > >
Re: [DISCUSS] Release Apache Taverna Mobile 1.0-incubating-RC1
Built successfully. md5 & sha1 checksums all match and also verified the GPG keys but your key has expired. does it make any issue? On Thu, Mar 28, 2019 at 9:53 PM Ian Dunlop wrote: > Hello, > > Please discuss the release of Apache Taverna Mobile 1.0-incubating-RC1 in > this thread. > > Cheers, > > Ian > > Sent from Mail for Windows 10 > > -- Warmest regards Sagar Software Developer Lattice Innovations Pvt. Ltd.
