[GitHub] incubator-edgent-website pull request #97: [WIP] changes for Edgent PR-309 (...

Github user queeniema commented on a diff in the pull request: https://github.com/apache/incubator-edgent-website/pull/97#discussion_r155388008 --- Diff: site/docs/power-of-edgent.md --- @@ -0,0 +1,417 @@ +--- +title: The Power of Apache Edgent +--- + +Edgent

[GitHub] incubator-edgent-website pull request #97: [WIP] changes for Edgent PR-309 (...

Github user queeniema commented on a diff in the pull request: https://github.com/apache/incubator-edgent-website/pull/97#discussion_r155387989 --- Diff: site/docs/power-of-edgent.md --- @@ -0,0 +1,417 @@ +--- +title: The Power of Apache Edgent +--- + +Edgent

[GitHub] incubator-edgent-website pull request #97: [WIP] changes for Edgent PR-309 (...

Github user queeniema commented on a diff in the pull request: https://github.com/apache/incubator-edgent-website/pull/97#discussion_r155386576 --- Diff: site/docs/faq.md --- @@ -4,51 +4,74 @@ title: FAQ ## What is Apache Edgent? -Edgent provides APIs and a

[GitHub] incubator-edgent-website pull request #97: [WIP] changes for Edgent PR-309 (...

Github user queeniema commented on a diff in the pull request: https://github.com/apache/incubator-edgent-website/pull/97#discussion_r155386261 --- Diff: site/docs/faq.md --- @@ -4,51 +4,74 @@ title: FAQ ## What is Apache Edgent? -Edgent provides APIs and a

[GitHub] incubator-edgent-website pull request #97: [WIP] changes for Edgent PR-309 (...

Github user queeniema commented on a diff in the pull request: https://github.com/apache/incubator-edgent-website/pull/97#discussion_r155386271 --- Diff: site/docs/faq.md --- @@ -4,51 +4,74 @@ title: FAQ ## What is Apache Edgent? -Edgent provides APIs and a

[GitHub] incubator-edgent-website pull request #97: [WIP] changes for Edgent PR-309 (...

Github user queeniema commented on a diff in the pull request: https://github.com/apache/incubator-edgent-website/pull/97#discussion_r155386244 --- Diff: site/docs/faq.md --- @@ -4,51 +4,74 @@ title: FAQ ## What is Apache Edgent? -Edgent provides APIs and a

[GitHub] incubator-edgent pull request #329: expect staged .zip too and .sha512

Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent/pull/329 ---

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

Agreed on all points regarding the zip. Since you offered, I updated the scripts to require it and the sha512 noted below :-) The verification includes verifying the tar.gz and zip contents are the same. On another topic, [1] says the suffix MUST be sha512 for a SHA 512 sum (which in fact is

[GitHub] incubator-edgent pull request #329: expect staged .zip too and .sha512

GitHub user dlaboss opened a pull request: https://github.com/apache/incubator-edgent/pull/329 expect staged .zip too and .sha512 You can merge this pull request into a Git repository by running: $ git pull https://github.com/dlaboss/incubator-edgent include-zip-and-sha512

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

Hi, > Regarding the pgp issue i guess you have to Import my Key somehow. But i'm No > expert on that. My key should be valid judging from the number of Apaches > that signed it. Eventually there is no path of trust and you need to import > it manually. The warning is fine - it just means that

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

Hi Dale, I just had a look at what the script was looking for. If releasing tar and zip i think we would have to do the checking for both types. I can add the other zip easily. But in that Case i would suggest adding that to the script and add one check to make sure the content is identical.

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

I’ll pull of that trust thread, thx. Another question re RC1: -Papache-release also generates a zip. I had expected we’d be releasing that too but it isn’t staged. At this time I’m fine if we just continue 1.2.0 with only the tar.gz but if you also want to stage the zip that's fine too. I

[GitHub] incubator-edgent pull request #328: Fix JAVA_SUPPORT.md markdown

Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent/pull/328 ---

[GitHub] incubator-edgent pull request #328: Fix JAVA_SUPPORT.md markdown

GitHub user dlaboss opened a pull request: https://github.com/apache/incubator-edgent/pull/328 Fix JAVA_SUPPORT.md markdown fix `` portion of jar name not getting rendered You can merge this pull request into a Git repository by running: $ git pull

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

I think in the gpg GUI Tool you also have to explicitly "trust" a Key. Otherwise its Just a Key. Chris Outlook for Android herunterladen From: Dale LaBossiere Sent: Wednesday, December 6, 2017 5:31:03 PM To:

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

I hear your pain :-) FWIW, I did import your key using the (possibly incomplete?) directions reported by the script. That’s why I was wondering if you saw the same thing for 1.2.0 and 1.1.0. I did what it told me to below when it failed the 1st time I ran it. buildTools/download_edgent_asf.sh

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

Hi Dale, I'm still on the task of manually deleting Things. Will continue tomorrow. Have to manually delete at least 4 Files for every artifact one at a time :-( Regarding the pgp issue i guess you have to Import my Key somehow. But i'm No expert on that. My key should be valid judging from

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

Thx re the nexus content. I’m getting a gpg warning validating the 1.2.0RC1 bundle signature that I don’t get when downloading/validating 1.1.0. Might your KEY changes have an issue or you didn’t “published” your key or such? Or maybe it’s just that with 1.1.0 I’m just validating something that I

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

Hi Dale, I guess I updated the KEY manually and it seems to be ok the way it is now. Regarding stuff in Nexus, we should remove before hitting the “release” button: - Intermediate poms are important as they are defined as “parent” of other artifacts. Maven downloads them in order to know the

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

Re the KEYS, please update the file in the incubator-edgent source repo. FWI, the 1.0.0 and 1.1.0 staging areas are empty because the "publishing the release” process is supposed to *move* the exact staged/voted artifacts to the release area. I see the our buildTools/publish_release.sh script

Re: [DISCUSS] Apache Edgent (Incubating) 1.2.0 RC1

Seems my mail hadn’t updated before I sent this reply. I see you’ve done some things regarding the nexus content, so ignore that part of the following until I get up to date :-) > On Dec 6, 2017, at 9:23 AM, Dale LaBossiere wrote: > > I’m sure I followed some Apache

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

Hi Dale, So, I updated the scripts, deployed the RC in the correct area (I wonder why the other 1.0.0 and 1.1.0 areas are empty. Unfortunately, I had to test myself to the right solution by running the scripts and fine tuning my deployment and the scripts. But now I think we have a working

Re: [VOTE] Apache Edgent (Incubating) 1.2.0 RC1

Ok … little update: I noticed that I still had to manually deploy the rc to the apache svn distribution area. So please use this url instead: https://dist.apache.org/repos/dist/dev/incubator/edgent/1.2.0-incubating/rc1/ I also updated the download and check scripts to work with the new

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

HI Dale, as I mentioned in the other DISCUSS thread I already noticed this shortcoming. I think the following path should be ok for us to follow: 1. I manually add my pgp key to the list in KEYS in SVN 2. I manually add the files created by the assembly plugin to SVN 3. We continue the voting