You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Denis Magda <dm...@apache.org> on 2018/12/10 19:45:03 UTC
Re: [Fwd: Returned post for announce@apache.org]
Forwarding to the dev list.
*Prachi*, could you please help us with 3-5? It requires minor updates on
the webpage.
*Sergey K.*, *Peter*, could you assist with 1 and 2?
--
Denis
On Fri, Dec 7, 2018 at 11:19 PM Nikolay Izhikov <ni...@apache.org> wrote:
> Hello, Igniters.
>
> Seems that our download page doesn't meet apache requirements.
> I think we should update the page according to apache rules.
>
> Who can do it?
>
>
>
> ---------- Forwarded message ----------
> From: announce-owner@apache.org
> To: nizhikov@apache.org
> Cc:
> Bcc:
> Date: 6 Dec 2018 13:02:57 -0000
> Subject: Returned post for announce@apache.org
>
> Hi! This is the ezmlm program. I'm managing the
> announce@apache.org mailing list.
>
> I'm sorry, your message (enclosed) was not accepted by the moderator.
> If the moderator has made any comments, they are shown below.
>
> >>>>> -------------------- >>>>>
> Sorry, but the download page does not meet requirements.
>
> 1) There is no link to the KEYS file
> https://www.apache.org/dist/ignite/KEYS
> This is necessary for validating downloaded artifacts
>
> 2) No description of how to validate downloads
>
> 3) There are links to dist.apache.org - that host is only intended for use
> during release preparation and publication.
> Use https://www.apache.org/dist/ignite/... instead.
>
> 4) There is a link to nightly builds.
> That is not allowed on a public download page, as the builds have not been
> voted on.
>
> 5) The paragraph introducing the binary artifact says:
>
> "In order to verify the release, we recommend that you download the
> official source distribution and verify the signatures of the downloaded
> files before opening them."
>
> This does not make sense in the binary section (it belongs in the source
> section and/or needs rewording).
> Nor is there any description of how to perform the verification.
>
> Please correct the page and resubmit the announce when that has been done.
>
> Sebb
> <<<<< -------------------- <<<<<
>
>
>
>
> ---------- Forwarded message ----------
> From: Nikolay Izhikov <ni...@apache.org>
> To: announce@apache.org
> Cc:
> Bcc:
> Date: Thu, 6 Dec 2018 15:02:21 +0300
> Subject: Fwd: [ANNOUNCE] Apache Ignite 2.7.0 Released
> The Apache Ignite Community is pleased to announce the release of
> Apache Ignite 2.7.0.
>
> Apache Ignite [1] is a memory-centric distributed database, caching,
> and processing platform for transactional, analytical, and streaming
> workloads delivering in-memory speeds at petabyte scale.
>
> This release introduce several major features and fixes some critical
> issues
> https://ignite.apache.org/releases/2.7.0/release_notes.html
>
> Download the latest Ignite version from here:
> https://ignite.apache.org/download.cgi
>
> Please let us know [2] if you encounter any problems.
>
> Regards,
> Nikolay Izhikov on behalf of Apache Ignite community
>
> [1] https://ignite.apache.org
> [2] https://ignite.apache.org/community/resources.html#ask
>
Re: [Fwd: Returned post for announce@apache.org]
Posted by vveider <mr...@gmail.com>.
ASC / SHA512 verification:
1. Download signing key: wget -c https://www.apache.org/dist/ignite/KEYS
2. Import key: gpg --import KEYS
3. Download release with signature and sha512 hash sum: wget -c
http://apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip
http://apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip.asc
http://apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip.sha512
4. Verify ASC signature: gpg --verify apache-ignite-2.7.0-src.zip.asc
apache-ignite-2.7.0-src.zip
5. Verify SHA512 hash sum: sha512sum -c apache-ignite-2.7.0-src.zip.sha512
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: [Fwd: Returned post for announce@apache.org]
Posted by Prachi Garg <pg...@gridgain.com>.
Ok, I'll fix issues 3-5.
On Mon, Dec 10, 2018 at 11:44 AM Denis Magda <dm...@apache.org> wrote:
> Forwarding to the dev list.
>
> *Prachi*, could you please help us with 3-5? It requires minor updates on
> the webpage.
>
> *Sergey K.*, *Peter*, could you assist with 1 and 2?
>
> --
> Denis
>
> On Fri, Dec 7, 2018 at 11:19 PM Nikolay Izhikov <ni...@apache.org>
> wrote:
>
> > Hello, Igniters.
> >
> > Seems that our download page doesn't meet apache requirements.
> > I think we should update the page according to apache rules.
> >
> > Who can do it?
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: announce-owner@apache.org
> > To: nizhikov@apache.org
> > Cc:
> > Bcc:
> > Date: 6 Dec 2018 13:02:57 -0000
> > Subject: Returned post for announce@apache.org
> >
> > Hi! This is the ezmlm program. I'm managing the
> > announce@apache.org mailing list.
> >
> > I'm sorry, your message (enclosed) was not accepted by the moderator.
> > If the moderator has made any comments, they are shown below.
> >
> > >>>>> -------------------- >>>>>
> > Sorry, but the download page does not meet requirements.
> >
> > 1) There is no link to the KEYS file
> > https://www.apache.org/dist/ignite/KEYS
> > This is necessary for validating downloaded artifacts
> >
> > 2) No description of how to validate downloads
> >
> > 3) There are links to dist.apache.org - that host is only intended for
> use
> > during release preparation and publication.
> > Use https://www.apache.org/dist/ignite/... instead.
> >
> > 4) There is a link to nightly builds.
> > That is not allowed on a public download page, as the builds have not
> been
> > voted on.
> >
> > 5) The paragraph introducing the binary artifact says:
> >
> > "In order to verify the release, we recommend that you download the
> > official source distribution and verify the signatures of the downloaded
> > files before opening them."
> >
> > This does not make sense in the binary section (it belongs in the source
> > section and/or needs rewording).
> > Nor is there any description of how to perform the verification.
> >
> > Please correct the page and resubmit the announce when that has been
> done.
> >
> > Sebb
> > <<<<< -------------------- <<<<<
> >
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: Nikolay Izhikov <ni...@apache.org>
> > To: announce@apache.org
> > Cc:
> > Bcc:
> > Date: Thu, 6 Dec 2018 15:02:21 +0300
> > Subject: Fwd: [ANNOUNCE] Apache Ignite 2.7.0 Released
> > The Apache Ignite Community is pleased to announce the release of
> > Apache Ignite 2.7.0.
> >
> > Apache Ignite [1] is a memory-centric distributed database, caching,
> > and processing platform for transactional, analytical, and streaming
> > workloads delivering in-memory speeds at petabyte scale.
> >
> > This release introduce several major features and fixes some critical
> > issues
> > https://ignite.apache.org/releases/2.7.0/release_notes.html
> >
> > Download the latest Ignite version from here:
> > https://ignite.apache.org/download.cgi
> >
> > Please let us know [2] if you encounter any problems.
> >
> > Regards,
> > Nikolay Izhikov on behalf of Apache Ignite community
> >
> > [1] https://ignite.apache.org
> > [2] https://ignite.apache.org/community/resources.html#ask
> >
>
Re: [Fwd: Returned post for announce@apache.org]
Posted by Prachi Garg <pg...@gridgain.com>.
For point 3, I cannot find where dist.apache.org is used...Can you please
point me to the right place?
On Thu, Dec 13, 2018 at 6:07 AM Peter Ivanov <pi...@gridgain.com> wrote:
> ASC / SHA512 verification:
>
> 1. Download signing key: wget -c https://www.apache.org/dist/ignite/KEYS
> 2. Import key: gpg --import KEYS
> 3. Download release with signature and sha512 hash sum: wget -c
> http://apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip
> http://apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip.asc
> http://apache.org/dist/ignite/2.7.0/apache-ignite-2.7.0-src.zip.sha512
> 4. Verify ASC signature: gpg --verify apache-ignite-2.7.0-src.zip.asc
> apache-ignite-2.7.0-src.zip
> 5. Verify SHA512 hash sum: sha512sum -c apache-ignite-2.7.0-src.zip.sha512
>
>
>
>
> On 10 Dec 2018, at 22:45, Denis Magda <dm...@apache.org> wrote:
>
> Forwarding to the dev list.
>
> *Prachi*, could you please help us with 3-5? It requires minor updates on
> the webpage.
>
> *Sergey K.*, *Peter*, could you assist with 1 and 2?
>
> --
> Denis
>
> On Fri, Dec 7, 2018 at 11:19 PM Nikolay Izhikov <ni...@apache.org>
> wrote:
>
>> Hello, Igniters.
>>
>> Seems that our download page doesn't meet apache requirements.
>> I think we should update the page according to apache rules.
>>
>> Who can do it?
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: announce-owner@apache.org
>> To: nizhikov@apache.org
>> Cc:
>> Bcc:
>> Date: 6 Dec 2018 13:02:57 -0000
>> Subject: Returned post for announce@apache.org
>>
>> Hi! This is the ezmlm program. I'm managing the
>> announce@apache.org mailing list.
>>
>> I'm sorry, your message (enclosed) was not accepted by the moderator.
>> If the moderator has made any comments, they are shown below.
>>
>> >>>>> -------------------- >>>>>
>> Sorry, but the download page does not meet requirements.
>>
>> 1) There is no link to the KEYS file
>> https://www.apache.org/dist/ignite/KEYS
>> This is necessary for validating downloaded artifacts
>>
>> 2) No description of how to validate downloads
>>
>> 3) There are links to dist.apache.org - that host is only intended for
>> use
>> during release preparation and publication.
>> Use https://www.apache.org/dist/ignite/.
>> <https://www.apache.org/dist/ignite/>.. instead.
>>
>> 4) There is a link to nightly builds.
>> That is not allowed on a public download page, as the builds have not been
>> voted on.
>>
>> 5) The paragraph introducing the binary artifact says:
>>
>> "In order to verify the release, we recommend that you download the
>> official source distribution and verify the signatures of the downloaded
>> files before opening them."
>>
>> This does not make sense in the binary section (it belongs in the source
>> section and/or needs rewording).
>> Nor is there any description of how to perform the verification.
>>
>> Please correct the page and resubmit the announce when that has been done.
>>
>> Sebb
>> <<<<< -------------------- <<<<<
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Nikolay Izhikov <ni...@apache.org>
>> To: announce@apache.org
>> Cc:
>> Bcc:
>> Date: Thu, 6 Dec 2018 15:02:21 +0300
>> Subject: Fwd: [ANNOUNCE] Apache Ignite 2.7.0 Released
>> The Apache Ignite Community is pleased to announce the release of
>> Apache Ignite 2.7.0.
>>
>> Apache Ignite [1] is a memory-centric distributed database, caching,
>> and processing platform for transactional, analytical, and streaming
>> workloads delivering in-memory speeds at petabyte scale.
>>
>> This release introduce several major features and fixes some critical
>> issues
>> https://ignite.apache.org/releases/2.7.0/release_notes.html
>>
>> Download the latest Ignite version from here:
>> https://ignite.apache.org/download.cgi
>>
>> Please let us know [2] if you encounter any problems.
>>
>> Regards,
>> Nikolay Izhikov on behalf of Apache Ignite community
>>
>> [1] https://ignite.apache.org
>> [2] https://ignite.apache.org/community/resources.html#ask
>>
>
>