Igniters,
Apache Ignite 2.7.0 release (RC2) has been accepted. 3 "+1" binding votes received: - Pavel Tupitsyn - Dmitriy Pavlov - Nikolay Izhikov Vote thread: http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html |
Nikolay,
Actually 4 "+1" binding. You did not count my "+1". :) On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov <[hidden email]> wrote: > Igniters, > > Apache Ignite 2.7.0 release (RC2) has been accepted. > > 3 "+1" binding votes received: > > - Pavel Tupitsyn > - Dmitriy Pavlov > - Nikolay Izhikov > > Vote thread: > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html > -- Alexey Kuznetsov |
Sorry, Alex.
I miss your +1. Thank you, very much for checking RC artifacts. вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov [hidden email]: > Nikolay, > > Actually 4 "+1" binding. > > You did not count my "+1". > > :) > > > On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov <[hidden email]> > wrote: > > > Igniters, > > > > Apache Ignite 2.7.0 release (RC2) has been accepted. > > > > 3 "+1" binding votes received: > > > > - Pavel Tupitsyn > > - Dmitriy Pavlov > > - Nikolay Izhikov > > > > Vote thread: > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html > > > > > -- > Alexey Kuznetsov > |
When are going to complete the post-release steps and announce the release?
Once the binaries are available on the website we need to release the docs. I'm ready to prepare a blog post for blogs.apache.org. -- Denis On Mon, Dec 3, 2018 at 11:14 PM Nikolay Izhikov <[hidden email]> wrote: > Sorry, Alex. > > I miss your +1. > Thank you, very much for checking RC artifacts. > > вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov [hidden email]: > > > Nikolay, > > > > Actually 4 "+1" binding. > > > > You did not count my "+1". > > > > :) > > > > > > On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov <[hidden email]> > > wrote: > > > > > Igniters, > > > > > > Apache Ignite 2.7.0 release (RC2) has been accepted. > > > > > > 3 "+1" binding votes received: > > > > > > - Pavel Tupitsyn > > > - Dmitriy Pavlov > > > - Nikolay Izhikov > > > > > > Vote thread: > > > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html > > > > > > > > > -- > > Alexey Kuznetsov > > > |
Yes, Denis.
I will do my best to complete release steps today. The only things that blocks me is bintray permissions. They required to upload rpm and deb packages to corresponding repository. I've created ticket to the INFRA [1] Seems, they, resolve it eventually. We discussed this issue with other Igniters and decided to do release without rpm and deb. When I got permissions, I release them too. [1] https://issues.apache.org/jira/browse/INFRA-17354 ср, 5 дек. 2018 г., 20:25 Denis Magda [hidden email]: > When are going to complete the post-release steps and announce the release? > Once the binaries are available on the website we need to release the docs. > > > I'm ready to prepare a blog post for blogs.apache.org. > > -- > Denis > > On Mon, Dec 3, 2018 at 11:14 PM Nikolay Izhikov <[hidden email]> > wrote: > > > Sorry, Alex. > > > > I miss your +1. > > Thank you, very much for checking RC artifacts. > > > > вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov [hidden email]: > > > > > Nikolay, > > > > > > Actually 4 "+1" binding. > > > > > > You did not count my "+1". > > > > > > :) > > > > > > > > > On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov <[hidden email]> > > > wrote: > > > > > > > Igniters, > > > > > > > > Apache Ignite 2.7.0 release (RC2) has been accepted. > > > > > > > > 3 "+1" binding votes received: > > > > > > > > - Pavel Tupitsyn > > > > - Dmitriy Pavlov > > > > - Nikolay Izhikov > > > > > > > > Vote thread: > > > > > > > > > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html > > > > > > > > > > > > > -- > > > Alexey Kuznetsov > > > > > > |
Hello Igniters,
The documentation for Apache Ignite 2.7.0 is now public on readme.io <https://apacheignite.readme.io/docs/>. -Prachi On Wed, Dec 5, 2018 at 9:35 AM Nikolay Izhikov <[hidden email]> wrote: > Yes, Denis. > > I will do my best to complete release steps today. > The only things that blocks me is bintray permissions. > They required to upload rpm and deb packages to corresponding repository. > > I've created ticket to the INFRA [1] > Seems, they, resolve it eventually. > > We discussed this issue with other Igniters and decided to do release > without rpm and deb. When I got permissions, I release them too. > > [1] https://issues.apache.org/jira/browse/INFRA-17354 > > ср, 5 дек. 2018 г., 20:25 Denis Magda [hidden email]: > > > When are going to complete the post-release steps and announce the > release? > > Once the binaries are available on the website we need to release the > docs. > > > > > > I'm ready to prepare a blog post for blogs.apache.org. > > > > -- > > Denis > > > > On Mon, Dec 3, 2018 at 11:14 PM Nikolay Izhikov <[hidden email]> > > wrote: > > > > > Sorry, Alex. > > > > > > I miss your +1. > > > Thank you, very much for checking RC artifacts. > > > > > > вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov [hidden email]: > > > > > > > Nikolay, > > > > > > > > Actually 4 "+1" binding. > > > > > > > > You did not count my "+1". > > > > > > > > :) > > > > > > > > > > > > On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov <[hidden email]> > > > > wrote: > > > > > > > > > Igniters, > > > > > > > > > > Apache Ignite 2.7.0 release (RC2) has been accepted. > > > > > > > > > > 3 "+1" binding votes received: > > > > > > > > > > - Pavel Tupitsyn > > > > > - Dmitriy Pavlov > > > > > - Nikolay Izhikov > > > > > > > > > > Vote thread: > > > > > > > > > > > > > > > > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html > > > > > > > > > > > > > > > > > -- > > > > Alexey Kuznetsov > > > > > > > > > > |
Nikolay,
Do you know when npm (and other thin client) package will be uploaded? - $ npm i apache-ignite-client --save - npm ERR! code E404 - npm ERR! 404 Not Found: apache-ignite-client@lates -- Roman On Thursday, December 6, 2018, 7:20:33 a.m. GMT+9, Prachi Garg <[hidden email]> wrote: Hello Igniters, The documentation for Apache Ignite 2.7.0 is now public on readme.io <https://apacheignite.readme.io/docs/>. -Prachi On Wed, Dec 5, 2018 at 9:35 AM Nikolay Izhikov <[hidden email]> wrote: > Yes, Denis. > > I will do my best to complete release steps today. > The only things that blocks me is bintray permissions. > They required to upload rpm and deb packages to corresponding repository. > > I've created ticket to the INFRA [1] > Seems, they, resolve it eventually. > > We discussed this issue with other Igniters and decided to do release > without rpm and deb. When I got permissions, I release them too. > > [1] https://issues.apache.org/jira/browse/INFRA-17354 > > ср, 5 дек. 2018 г., 20:25 Denis Magda [hidden email]: > > > When are going to complete the post-release steps and announce the > release? > > Once the binaries are available on the website we need to release the > docs. > > > > > > I'm ready to prepare a blog post for blogs.apache.org. > > > > -- > > Denis > > > > On Mon, Dec 3, 2018 at 11:14 PM Nikolay Izhikov <[hidden email]> > > wrote: > > > > > Sorry, Alex. > > > > > > I miss your +1. > > > Thank you, very much for checking RC artifacts. > > > > > > вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov [hidden email]: > > > > > > > Nikolay, > > > > > > > > Actually 4 "+1" binding. > > > > > > > > You did not count my "+1". > > > > > > > > :) > > > > > > > > > > > > On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov <[hidden email]> > > > > wrote: > > > > > > > > > Igniters, > > > > > > > > > > Apache Ignite 2.7.0 release (RC2) has been accepted. > > > > > > > > > > 3 "+1" binding votes received: > > > > > > > > > > - Pavel Tupitsyn > > > > > - Dmitriy Pavlov > > > > > - Nikolay Izhikov > > > > > > > > > > Vote thread: > > > > > > > > > > > > > > > > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html > > > > > > > > > > > > > > > > > -- > > > > Alexey Kuznetsov > > > > > > > > > > |
Hello, Roman.
Do we have release procedure for this pacakage? Let's develop one. Thin client developers, please,let me know, which artifacts should be uploaded to which package manager system. В Пн, 10/12/2018 в 04:30 +0000, Roman Shtykh пишет: > Nikolay, > Do you know when npm (and other thin client) package will be uploaded? > > - $ npm i apache-ignite-client --save > - npm ERR! code E404 > - npm ERR! 404 Not Found: apache-ignite-client@lates > > > -- Roman > > > On Thursday, December 6, 2018, 7:20:33 a.m. GMT+9, Prachi Garg <[hidden email]> wrote: > > Hello Igniters, > > The documentation for Apache Ignite 2.7.0 is now public on readme.io > <https://apacheignite.readme.io/docs/>. > > -Prachi > > On Wed, Dec 5, 2018 at 9:35 AM Nikolay Izhikov <[hidden email]> wrote: > > > Yes, Denis. > > > > I will do my best to complete release steps today. > > The only things that blocks me is bintray permissions. > > They required to upload rpm and deb packages to corresponding repository. > > > > I've created ticket to the INFRA [1] > > Seems, they, resolve it eventually. > > > > We discussed this issue with other Igniters and decided to do release > > without rpm and deb. When I got permissions, I release them too. > > > > [1] https://issues.apache.org/jira/browse/INFRA-17354 > > > > ср, 5 дек. 2018 г., 20:25 Denis Magda [hidden email]: > > > > > When are going to complete the post-release steps and announce the > > > > release? > > > Once the binaries are available on the website we need to release the > > > > docs. > > > > > > > > > I'm ready to prepare a blog post for blogs.apache.org. > > > > > > -- > > > Denis > > > > > > On Mon, Dec 3, 2018 at 11:14 PM Nikolay Izhikov <[hidden email]> > > > wrote: > > > > > > > Sorry, Alex. > > > > > > > > I miss your +1. > > > > Thank you, very much for checking RC artifacts. > > > > > > > > вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov [hidden email]: > > > > > > > > > Nikolay, > > > > > > > > > > Actually 4 "+1" binding. > > > > > > > > > > You did not count my "+1". > > > > > > > > > > :) > > > > > > > > > > > > > > > On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov <[hidden email]> > > > > > wrote: > > > > > > > > > > > Igniters, > > > > > > > > > > > > Apache Ignite 2.7.0 release (RC2) has been accepted. > > > > > > > > > > > > 3 "+1" binding votes received: > > > > > > > > > > > > - Pavel Tupitsyn > > > > > > - Dmitriy Pavlov > > > > > > - Nikolay Izhikov > > > > > > > > > > > > Vote thread: > > > > > > > > > > > > > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html > > > > > > > > > > > > > > > > > > > > > -- > > > > > Alexey Kuznetsov > > > > > > > > > |
AFAIK, there is no such procedure yet and it definitely requires introduction.
I guess, thin client developers should share the process of updating official repositories. > On 10 Dec 2018, at 09:49, Nikolay Izhikov <[hidden email]> wrote: > > Hello, Roman. > > Do we have release procedure for this pacakage? > Let's develop one. > > Thin client developers, please,let me know, which artifacts should be uploaded to which package manager system. > > > В Пн, 10/12/2018 в 04:30 +0000, Roman Shtykh пишет: >> Nikolay, >> Do you know when npm (and other thin client) package will be uploaded? >> >> - $ npm i apache-ignite-client --save >> - npm ERR! code E404 >> - npm ERR! 404 Not Found: apache-ignite-client@lates >> >> >> -- Roman >> >> >> On Thursday, December 6, 2018, 7:20:33 a.m. GMT+9, Prachi Garg <[hidden email]> wrote: >> >> Hello Igniters, >> >> The documentation for Apache Ignite 2.7.0 is now public on readme.io >> <https://apacheignite.readme.io/docs/>. >> >> -Prachi >> >> On Wed, Dec 5, 2018 at 9:35 AM Nikolay Izhikov <[hidden email]> wrote: >> >>> Yes, Denis. >>> >>> I will do my best to complete release steps today. >>> The only things that blocks me is bintray permissions. >>> They required to upload rpm and deb packages to corresponding repository. >>> >>> I've created ticket to the INFRA [1] >>> Seems, they, resolve it eventually. >>> >>> We discussed this issue with other Igniters and decided to do release >>> without rpm and deb. When I got permissions, I release them too. >>> >>> [1] https://issues.apache.org/jira/browse/INFRA-17354 >>> >>> ср, 5 дек. 2018 г., 20:25 Denis Magda [hidden email]: >>> >>>> When are going to complete the post-release steps and announce the >>> >>> release? >>>> Once the binaries are available on the website we need to release the >>> >>> docs. >>>> >>>> >>>> I'm ready to prepare a blog post for blogs.apache.org. >>>> >>>> -- >>>> Denis >>>> >>>> On Mon, Dec 3, 2018 at 11:14 PM Nikolay Izhikov <[hidden email]> >>>> wrote: >>>> >>>>> Sorry, Alex. >>>>> >>>>> I miss your +1. >>>>> Thank you, very much for checking RC artifacts. >>>>> >>>>> вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov [hidden email]: >>>>> >>>>>> Nikolay, >>>>>> >>>>>> Actually 4 "+1" binding. >>>>>> >>>>>> You did not count my "+1". >>>>>> >>>>>> :) >>>>>> >>>>>> >>>>>> On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov <[hidden email]> >>>>>> wrote: >>>>>> >>>>>>> Igniters, >>>>>>> >>>>>>> Apache Ignite 2.7.0 release (RC2) has been accepted. >>>>>>> >>>>>>> 3 "+1" binding votes received: >>>>>>> >>>>>>> - Pavel Tupitsyn >>>>>>> - Dmitriy Pavlov >>>>>>> - Nikolay Izhikov >>>>>>> >>>>>>> Vote thread: >>>>>>> >>>>>>> >>>>>>> >>> >>> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Alexey Kuznetsov >>>>>> >>> >>> |
NodeJs client:
-------------- Instruction - https://github.com/nobitlost/ignite/blob/ignite-7777-docs/modules/platforms/nodejs/README.md#publish-ignite-nodejs-client-on-npmjscom-instruction Uploaded - https://www.npmjs.com/package/apache-ignite-client PHP client: ----------- Instruction - https://github.com/nobitlost/ignite/blob/ignite-7783-docs/modules/platforms/php/README.md#release-the-client-in-the-php-package-repository-instruction Cannot be uploaded on Packagist as the client should be in a dedicated repository for that - https://issues.apache.org/jira/browse/IGNITE-7783?focusedCommentId=16595476&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16595476 Installation from the sources works. Python client: -------------- Dmitry M. will provide the details. -Alexey 10.12.2018 14:15, Petr Ivanov пишет: > AFAIK, there is no such procedure yet and it definitely requires introduction. > I guess, thin client developers should share the process of updating official repositories. > > >> On 10 Dec 2018, at 09:49, Nikolay Izhikov <[hidden email]> wrote: >> >> Hello, Roman. >> >> Do we have release procedure for this pacakage? >> Let's develop one. >> >> Thin client developers, please,let me know, which artifacts should be uploaded to which package manager system. >> >> >> В Пн, 10/12/2018 в 04:30 +0000, Roman Shtykh пишет: >>> Nikolay, >>> Do you know when npm (and other thin client) package will be uploaded? >>> >>> - $ npm i apache-ignite-client --save >>> - npm ERR! code E404 >>> - npm ERR! 404 Not Found: apache-ignite-client@lates >>> >>> >>> -- Roman >>> >>> >>> On Thursday, December 6, 2018, 7:20:33 a.m. GMT+9, Prachi Garg <[hidden email]> wrote: >>> >>> Hello Igniters, >>> >>> The documentation for Apache Ignite 2.7.0 is now public on readme.io >>> <https://apacheignite.readme.io/docs/>. >>> >>> -Prachi >>> >>> On Wed, Dec 5, 2018 at 9:35 AM Nikolay Izhikov <[hidden email]> wrote: >>> >>>> Yes, Denis. >>>> >>>> I will do my best to complete release steps today. >>>> The only things that blocks me is bintray permissions. >>>> They required to upload rpm and deb packages to corresponding repository. >>>> >>>> I've created ticket to the INFRA [1] >>>> Seems, they, resolve it eventually. >>>> >>>> We discussed this issue with other Igniters and decided to do release >>>> without rpm and deb. When I got permissions, I release them too. >>>> >>>> [1] https://issues.apache.org/jira/browse/INFRA-17354 >>>> >>>> ср, 5 дек. 2018 г., 20:25 Denis Magda [hidden email]: >>>> >>>>> When are going to complete the post-release steps and announce the >>>> >>>> release? >>>>> Once the binaries are available on the website we need to release the >>>> >>>> docs. >>>>> >>>>> >>>>> I'm ready to prepare a blog post for blogs.apache.org. >>>>> >>>>> -- >>>>> Denis >>>>> >>>>> On Mon, Dec 3, 2018 at 11:14 PM Nikolay Izhikov <[hidden email]> >>>>> wrote: >>>>> >>>>>> Sorry, Alex. >>>>>> >>>>>> I miss your +1. >>>>>> Thank you, very much for checking RC artifacts. >>>>>> >>>>>> вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov [hidden email]: >>>>>> >>>>>>> Nikolay, >>>>>>> >>>>>>> Actually 4 "+1" binding. >>>>>>> >>>>>>> You did not count my "+1". >>>>>>> >>>>>>> :) >>>>>>> >>>>>>> >>>>>>> On Tue, Dec 4, 2018 at 4:28 AM Nikolay Izhikov <[hidden email]> >>>>>>> wrote: >>>>>>> >>>>>>>> Igniters, >>>>>>>> >>>>>>>> Apache Ignite 2.7.0 release (RC2) has been accepted. >>>>>>>> >>>>>>>> 3 "+1" binding votes received: >>>>>>>> >>>>>>>> - Pavel Tupitsyn >>>>>>>> - Dmitriy Pavlov >>>>>>>> - Nikolay Izhikov >>>>>>>> >>>>>>>> Vote thread: >>>>>>>> >>>>>>>> >>>>>>>> >>>> >>>> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Alexey Kuznetsov >>>>>>> >>>> >>>> > |
In reply to this post by Nikolay Izhikov-2
Nikolay, Petr,
I have already registered the package `pyignite` on PyPI[1]. The person who is going to take the responsibility of maintaining it should create an account on PyPI and mail me in private, so that I can grant them the necessary rights. They also must install twine[3]. The process of packaging is well described in the packaging tutorial[2]. In the nutshell, the maintainer must do the following: 1. Clone/pull the sources from the git repository, 2. Enter the directory in which the `setup.py` is resides (“the setup directory”), in our case it is `modules/platforms/python`. 3. Create the packages with the command `python3 setup.py sdist bdist_wheel`. The packages will be created in `modules/platforms/python/dist` folder. 4. Upload packages with twine: `twine upload dist/*`. It is very useful to have a dedicated Python virtual environment prepared to perform steps 3-4. Just do an editable install of `pyignite` into that environment from the setup directory: `pip3 install -e .` You can also install twine (`pip install twine`) in it. Consider also making a `.pypirc` file to save time on logging in to PyPI. Newest version of `twine` is said to support keyrings on Linux and Mac, but I have not tried this yet. [1] https://pypi.org/project/pyignite/ [2] https://packaging.python.org/tutorials/packaging-projects/ [3] https://twine.readthedocs.io/en/latest/ Some other notes on PyPI and versioning. - The package version is located in the `setup.py`, it is a `version` argument of the `setuptools.setup()` function. Editing the `setup.py` is the only way to set the package version. - You absolutely can not replace a package in PyPI (hijacking prevention). If you have published the package by mistake, all you can do is delete the unwanted package, increment the version counter in `setup.py`, and try again. - If you upload the package through the web interface of PyPI (without twine), the package description will be garbled. Web interface does not support markdown. Anyway, I would like to join in the congratulations on successful release. Kudos to the team. On 12/10/18 4:49 PM, Nikolay Izhikov wrote: > Hello, Roman. > > Do we have release procedure for this pacakage? > Let's develop one. > > Thin client developers, please,let me know, which artifacts should be uploaded to which package manager system. > |
Free forum by Nabble | Edit this page |