Denis,
I would suggest to stay on a safe ground and associate an every commit
with a ticket until we have a Community decision about relaxing this
process for documentation tickets. As far as I remember sometimes as
an exception we use a single ticket number for multiple commits (e.g.
fix
Folks,
Apologize for the disruption. The message didn't appear in my inbox even
when you CC-ed me directly. I was notified about the issue only today.
Anyway, the licensing issue is fixed and the commit is back to the master.
Speaking of the process, it can't be 100% the same for tech docs
Folks,
Should we also reopen the issue [1] since the change has been reverted?
Should we not only merge the changes to the master branch but also
cherry-pick them to the ignite-2.9 branch since docs are related to
2.9 release?
[1] https://issues.apache.org/jira/browse/IGNITE-7595
On Thu, 8 Oct
Denis,
I've tried to quickly add licenses to the files, but there are simply too
many different file types in the change. I reverted the original commit and
the dependent one about the continuous query guarantees (which, btw, was
merged without ticket name and with a merge commit).
Please make
Wow, I've got a
Files with unapproved licenses:
docs/_config.yml
docs/_plugins/asciidoctor-extensions.rb
docs/_includes/right-nav.html
docs/_includes/left-nav.html
docs/_includes/header.html
docs/_includes/toc.html
docs/_includes/section-toc.html
docs/_includes/copyright.html
Denis, folks,
The mentioned commit breaks our license checks.
Is someone working on the fix at the moment? If not it might be
simpler to revert the commit and push a fixed version later on. Also
it looks sad that so massive contribution was pushed without bot visa
[1].
[1]
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
