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
Hi,
I have raised a tiny PR for following issue:
IGNITE-12997 Rename pub-sub module to pub-sub-ext
https://issues.apache.org/jira/browse/IGNITE-12997
PR : https://github.com/apache/ignite-extensions/pull/13
Please take a look and share your thoughts.
Regards,
Saikat
Saikat Maitra created IGNITE-12997:
--
Summary: Rename pub-sub module to pub-sub-ext
Key: IGNITE-12997
URL: https://issues.apache.org/jira/browse/IGNITE-12997
Project: Ignite
Issue Type:
Hi,
I wanted to discuss the idea of creating Apache Ignite mascot and if it is
something we would be interested. I was recently following the process of
creating a mascot Firefly[1] in Apache Beam project and absolutely loved
the concept.
Hi,
I am thinking we can create a new repo under ASF and move the web-console
module. We can name the repo may be like ignite-web-console or
ignite-tools. The reason for suggesting ASF repo is since the web-console
already has Apache 2.0 license we can continue to maintain same license.
Also
Maxim,
Thank your for a clarification. Follow-up questions:
1. Do we need both "pr" and "push" builds? Is not it enough to have only "pr"?
2. What do we build regularly on TC? I suppose it works similarly to
Travis "push" mode. Is it worth (and possible) to consider switching
to "pr" mode?
P.S.
Merged to master.
Best regards,
Ivan Pavlukhin
чт, 7 мая 2020 г. в 19:45, Dmitriy Pavlov :
>
> IMO, we can remove. This badge does not work since GitHub started to
> cache images. Now TC's status .SVG does not work properly.
>
> чт, 7 мая 2020 г. в 09:25, Ivan Pavlukhin :
>
> > Folks,
> >
> > I
