Re: [DISCUSSION] ASF Board Report Draft, May 2020
Dmitry, thanks for taking care of this. Btw, I remember that the report generation UI had a sort of "Send Email" checkmark that allowed us to do both - add the report to the board's agenda and also generate an email template for dev@ignite.apache.org. Do you still see such a checkmark/button? If they removed this capability from the interface, would you mind sending a copy of a final report to @dev? - Denis On Sun, May 10, 2020 at 6:22 AM Dmitriy Pavlov wrote: > Hi Denis, > > Thank you for your valuable proposals, I appreciate it. > > I've updated the description. Eventually, we need to update it in the ASF > records, I guess at projects.apache.org. Report's description is taken > from > somewhere else and is auto-generated. > > I've added all points to project or community activities sections (e.g. > talks go to the community). > > Since where was Spring Boot Extensions 1.0.0 release announce at the list, > I've added it as well to the report. > > The report is now filed into the board meeting agenda. > > Sincerely, > Dmitriy Pavlov > > > пт, 8 мая 2020 г. в 00:49, Denis Magda : > > > Hi Dmitry, thanks! > > > > Please add the following to the project activity section: > > > >- Released a new version of the Apache Ignite website: > >https://ignite.apache.org > >- Prepared a public roadmap with significant improvements planned for > >the rest of 2020: > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap > >- Flume, flinks and some other extensions have been migrated to the > >extensions repository: > >https://github.com/apache/ignite-extensions/tree/master/modules > >- Community members gave 19 public online and offline presentations > >about the project since the beginning of 2020. Around 8 talks are yet > > to be > >presented and even more to follow: > > https://ignite.apache.org/events.html > > > > To my knowledge, the Spring Boot extension has been already released ( > > https://apacheignite-mix.readme.io/docs/spring-boot). @Nikolay Izhikov > > , is it ready to be announced? > > > > Also, I would suggest using this as a definition of the project (what > > Ignite is) - Apache Ignite® is a horizontally scalable, fault-tolerant > > distributed in-memory computing platform for building real-time > > applications that can process terabytes of data with in-memory speed. > > > > - > > Denis > > > > > > On Thu, May 7, 2020 at 7:46 AM Dmitriy Pavlov > wrote: > > > > > Hi Igniters, > > > > > > To increase involvement of each member of the community and increase > > > transparency I'd like to share report draft for ASF board with all dev@ > > > community. Thanks to Ivan P. for this idea. > > > > > > What would you like to add to this report? Major features, events, > > popular > > > publications could be mentioned in the report (main manual sections are > > > community and project activity, and issues - if any). Let's make it > more > > > representative and useful. I'm going to publish it during weekend. > Please > > > find report draft below and share your thoughts. > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > ## Description: > > > The mission of Ignite is the creation and maintenance of software > related > > > to > > > High-performance, integrated and distributed in-memory platform for > > > computing > > > and transacting on large-scale data sets in real-time > > > > > > ## Issues: > > > There are no issues requiring board attention. > > > > > > ## Membership Data: > > > Apache Ignite was founded 2015-08-19 (5 years ago) > > > There are currently 50 committers and 34 PMC members in this project. > > > The Committer-to-PMC ratio is roughly 7:5. > > > > > > Community changes, past quarter: > > > - Maxim Muzafarov was added to the PMC on 2020-04-28 > > > - Slava Koptilin was added as committer on 2020-02-15 > > > > > > ## Project Activity: > > > 2.8.0 was released on 2020-03-03. > > > Spring boot starter was voted to be released. > > > Apache Ignite 2.8.1 release is under preparation. > > > > > > ## Community Health: > > > Activity at development related mailing lists (dev@, issues@, > > > notifications@) > > > > > > increased in compare to past quarter (+30..40%) > > > Commits count this quarter is slightly less (-17%) > > > > > >
[jira] [Created] (IGNITE-12999) Fix broken ZookeeperDiscoverySpiSslTest.testIgniteSslWrongPort
Ivan Daschinskiy created IGNITE-12999: - Summary: Fix broken ZookeeperDiscoverySpiSslTest.testIgniteSslWrongPort Key: IGNITE-12999 URL: https://issues.apache.org/jira/browse/IGNITE-12999 Project: Ignite Issue Type: Test Reporter: Ivan Daschinskiy Assignee: Ivan Daschinskiy After merging [IGNITE-12992|https://issues.apache.org/jira/browse/IGNITE-12992] to master, mentioned above test, that was initially broken, starts to fail in master. This is because actual zk connection string was set, but not wrong. So node joins and assertion fails. Fix is trivial. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] Apache URL for TC bot
Ivan, Good idea. +1 to have the right domain name. I can imagine that we can go even further and completely move TC.Bot to some public cloud storage. For example, Amazon can provide promotional credits for open source projects [1]. [1] https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects/ On Mon, 11 May 2020 at 11:35, Ivan Pavlukhin wrote: > > Igniters, > > As you might know currently TC bot has a domain name in a GridGain > domain [1]. What do you think should we assign a name in an Apache > domain to the bot? > > [1] https://mtcga.gridgain.com/ > > Best regards, > Ivan Pavlukhin
Re: Github pull requests are not linked automatically to jira tickets.
Pavel, Thank you! I merged the PR. Let's see that PR linking to JIRA and everything else work fine. Best regards, Ivan Pavlukhin пт, 8 мая 2020 г. в 14:45, Pavel Pereslegin : > > Igniters, > > ticket created [1], please take a look at the proposed changes [2]. > > [1] https://issues.apache.org/jira/browse/IGNITE-12993 > [2] https://github.com/apache/ignite/pull/7784/files > > пт, 8 мая 2020 г. в 12:02, Maxim Muzafarov : > > > > Pavel, > > > > > > I have no objections. Let's file a ticket. > > > > On Fri, 8 May 2020 at 08:04, Ivan Pavlukhin wrote: > > > > > > Pavel, > > > > > > Thank you for starting this discussion! > > > > > > Controlling all this repo options on our side sounds very attractive. > > > > > > Personally I do not have any arguments about the proposal. > > > > > > Best regards, > > > Ivan Pavlukhin > > > > > > чт, 7 мая 2020 г. в 17:39, Pavel Pereslegin : > > > > > > > > Igniters, > > > > > > > > recent github pull requests are not automatically linked to the jira > > > > tickets. > > > > > > > > Infra advises creating a yaml configuration in the root of the > > > > repository > > > > with the settings for the github bot [1]. > > > > Examples of such configuration in Hive [2] and HBase [3]. > > > > I suggest the following settings for Ignite [4]. > > > > > > > > If there are no objections, I'll file a ticket for this. > > > > > > > > [1] https://issues.apache.org/jira/browse/INFRA-20177 > > > > [2] https://github.com/apache/hbase/blob/master/.asf.yaml > > > > [3] https://github.com/apache/hive/blob/master/.asf.yaml > > > > [4] https://gist.github.com/xtern/572cbc7d4a7916f6e933fbafe5034492
[jira] [Created] (IGNITE-12998) Fix a typo in CONTRIBUTING.md
Ivan Pavlukhin created IGNITE-12998: --- Summary: Fix a typo in CONTRIBUTING.md Key: IGNITE-12998 URL: https://issues.apache.org/jira/browse/IGNITE-12998 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin CoPDoC abbreviation should be spelled properly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[DISCUSS] Apache URL for TC bot
Igniters, As you might know currently TC bot has a domain name in a GridGain domain [1]. What do you think should we assign a name in an Apache domain to the bot? [1] https://mtcga.gridgain.com/ Best regards, Ivan Pavlukhin
[DISCUSS] TC bot instructions for open source contributors
Hi, Recently I faced problems explaining how a code contribution for Ignite should be checked with TC bot. Initially I thought that this process is well defined in our beloved contribution guidelines [1, 2]. But as I see neither of them explains the process directly. Finally I found better instructions [3]. So, the questions is should not we mention TC bot as earlier as possible? Naively I would like to see some words about it in CONTRIBUTING.md [1]. Please, share your thoughts on this! [1] https://github.com/apache/ignite/blob/master/CONTRIBUTING.md [2] https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute [3] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Teamcity+Bot#ApacheIgniteTeamcityBot-HowtocheckaPRwiththeTCBot Best regards, Ivan Pavlukhin
Re: [MTCGA]: new failures in builds [5293839] needs to be handled
Hi Ivan, Could you please take look into a failing test mentioned by bot? Best regards, Ivan Pavlukhin вс, 10 мая 2020 г. в 04:16, : > > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > > If your changes can lead to this failure(s): We're grateful that you were a > volunteer to make the contribution to this project, but things change and you > may no longer be able to finalize your contribution. > Could you respond to this email and indicate if you wish to continue and fix > test failures or step down and some committer may revert you commit. > > *New test failure in master > ZookeeperDiscoverySpiSslTest.testIgniteSslWrongPort > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5364809324777472206=%3Cdefault%3E=testDetails > Changes may lead to failure were done by > - ivan daschinskiy > https://ci.ignite.apache.org/viewModification.html?modId=901644 > > - Here's a reminder of what contributors were agreed to do > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute > - Should you have any questions please contact dev@ignite.apache.org > > Best Regards, > Apache Ignite TeamCity Bot > https://github.com/apache/ignite-teamcity-bot > Notification generated at 04:16:37 10-05-2020
Re: IGNITE-12976: Invalid SQL syntax for NULLS LAST / NULLS FIRST in IgniteQueryGenerator
Hi Mikhail, Thank you in you help with this! I left some comments in JIRA [1]. [1] https://issues.apache.org/jira/browse/IGNITE-12976 Best regards, Ivan Pavlukhin вс, 10 мая 2020 г. в 10:49, Denis Magda : > > Hi Mikhail, > > Thanks for taking care of this. Please check JIRA. Changes look good to me > but I would add a test to ensure that issue doesn't bubble up in the future. > > - > Denis > > > On Sun, May 10, 2020 at 12:33 AM Mikhail Kostyuckovich < > m.kostyuckov...@irdeto.com> wrote: > > > Hello Ignite Developers, > > > > > > I have prepared a small PR fixing the following issue related to Spring > > Data integration: > > > > IGNITE-12976: Invalid SQL syntax for NULLS LAST / NULLS FIRST in > > IgniteQueryGenerator > > https://issues.apache.org/jira/browse/IGNITE-12976 > > > > > > Could you please have a look and approve/accept? > > https://github.com/apache/ignite/pull/7766 > > > > Many thanks in advance! > > > > > > Kind regards, > > Mikhail Kostyuckovich > >
