Hi guys!

Alexey, I do confirm that some of the issues are already resolved (for
example, IGNITE-14658 <https://issues.apache.org/jira/browse/IGNITE-14658> is
already documented).
What is more, some of the tickets seem to be minor or "very internal"
things that do not change the behaviour/are not accessible for users,
including tests' improvements.

I would say that most of these tickets should be reflected only in the
Release notes, while some should even be omitted.

Alexey, could you or someone else please look through these tickets once
again and say which of them are worth documenting?
Then I'll be able to give the approximate time estimates.

Thank you!

Regards,
Nikita

пн, 5 июл. 2021 г. в 12:20, Alex Plehanov <plehanov.a...@gmail.com>:

> Alexey,
>
> Some of these tickets are already documented. Do we need to clear the "Docs
> Required" flag if documentation for the ticket has been merged to the
> master and release branch? AFAIK we didn't do that for previous releases.
>
> пн, 5 июл. 2021 г. в 13:53, Alexey Gidaspov <olive.c...@gmail.com>:
>
> > Hi, Nikita!
> >
> > As I can see, these are the tickets we need to document [1]
> >
> > Can you tell me how long it will take to complete work on documentation?
> >
> > [1]
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20'Ignite'%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20('2.11')%20AND%20cf%5B12313620%5D%20%3D%20%22Docs%20Required%22
> >
> > On 2021/06/09 10:06:09, Nikita Safonov <vlasovpavel2...@gmail.com>
> wrote:
> > > Hello Igniters!
> > >
> > > I guess that AI 2.11 will include documentation work.
> > > I'll be glad to help with this.
> > > And I'll be happy to know the scope of features that we need to
> document.
> > >
> > > Regards,
> > > Nikita
> > >
> > > пт, 4 июн. 2021 г. в 03:50, 18624049226 <18624049...@163.com>:
> > >
> > > > hello,
> > > >
> > > > can someone can help to merge the following patch into master?
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-12852
> > > >
> > > > This patch has been completed for a long time, and I think it is a
> > > > valuable one.
> > > >
> > > > 在 2021/6/3 下午11:12, Dmitry Pavlov 写道:
> > > > > Sure, thanks for your reply
> > > > >
> > > > > Folks, could you please advice how to setup JIRA account
> integration
> > for
> > > > non-committers?
> > > > >
> > > > > For the page
> > > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.11
> > > > > I can see all issues, but Alexey's login seems to be not
> sufficient.
> > Can
> > > > wiki admins set up smth? Or Alexey should do some setup on his own?
> > > > >
> > > > > On 2021/06/03 14:55:25, Maksim Timonin <timonin.ma...@gmail.com>
> > wrote:
> > > > >> I mean I'm OK to release it with 2.12. So, I am glad to hear there
> > are
> > > > >> chances for 2.11, but I guess we can postpone it.
> > > > >>
> > > > >>
> > > > >> On Thu, Jun 3, 2021 at 5:39 PM Dmitry Pavlov <dpav...@apache.org>
> > > > wrote:
> > > > >>
> > > > >>> ok, Maksim, keep us posted.
> > > > >>>
> > > > >>> We're in the middle of paperwork rigth now, so there is a chance
> ))
> > > > >>>
> > > > >>> On 2021/06/03 14:30:55, Maksim Timonin <timonin.ma...@gmail.com>
> > > > wrote:
> > > > >>>>> Regarding non-SQL index API it really depends on readiness. I
> > guess
> > > > if
> > > > >>> it
> > > > >>>> is not in the master, we can skip and release it next time.
> > > > >>>>
> > > > >>>> Hi, Dmitry! Yes, currently it is on review. I'm OK to release it
> > > > within
> > > > >>> the
> > > > >>>> next release.
> > > > >>>>
> > > > >>>> On Thu, Jun 3, 2021 at 5:26 PM Dmitry Pavlov <
> dpav...@apache.org>
> > > > wrote:
> > > > >>>>
> > > > >>>>> Hi Alexey,
> > > > >>>>>
> > > > >>>>> Releasing master as-is makes sence for me.
> > > > >>>>>
> > > > >>>>> Regarding non-SQL index API it really depends on readiness. I
> > guess
> > > > if
> > > > >>> it
> > > > >>>>> is not in the master, we can skip and release it next time.
> > > > >>>>>
> > > > >>>>> We've a bit overdue initial scope freeze date. It's not a big
> > deal,
> > > > but
> > > > >>>>> still makes sense to start discussion, create and share wiki
> > page and
> > > > >>>>> create branch.
> > > > >>>>>
> > > > >>>>> Since committer privileges required to create branch, could you
> > > > please
> > > > >>>>> notify me in advance.
> > > > >>>>>
> > > > >>>>> Sincerely,
> > > > >>>>> Dmitriy Pavlov
> > > > >>>>>
> > > > >>>>> On 2021/06/03 14:08:34, �������������� ���������������� <
> > > > >>>>> olive.c...@gmail.com> wrote:
> > > > >>>>>> :scope:
> > > > >>>>>>
> > > > >>>>>> Here is a list [1] of 195 tickets, i picked for Apache Ignite
> > 2.11
> > > > >>>>> release
> > > > >>>>>> Let's start discussion
> > > > >>>>>>
> > > > >>>>>> [1]
> > > > >>>
> > > >
> >
> https://issues.apache.org/jira/browse/IGNITE-14781?jql=project%20%3D%20IGNITE%20%20AND%20status%20%20%3D%20Resolved%20and%20fixVersion%20%3D%202.11%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> > > > >>>>>> On 2021/05/13 14:27:33, Dmitry Pavlov <dpav...@apache.org>
> > wrote:
> > > > >>>>>>> Hi Alexey,
> > > > >>>>>>>
> > > > >>>>>>> :pmc to sign distribution:
> > > > >>>>>>> Formally, only PMC member can be a release manager, so part
> of
> > > > >>>>> activities should be picked up by committer and PMC member. If
> > noone
> > > > >>> else
> > > > >>>>> want to help you here, I would.
> > > > >>>>>>> :timeline:
> > > > >>>>>>> And, could you estimate all phases of the release.
> > > > >>>>>>>
> > > > >>>>>>> :scope:
> > > > >>>>>>> I guess we can just pick up master current state and release
> > it.
> > > > >>> But
> > > > >>>>> if someone has some ideas if we should wait for particular
> > feature to
> > > > >>> be
> > > > >>>>> completed before branch divergence/release candidate build,
> > please
> > > > let
> > > > >>> know.
> > > > >>>>>>> Sincerely,
> > > > >>>>>>> Dmitriy Pavlov
> > > > >>>>>>>
> > > > >>>>>>> On 2021/05/13 09:45:02, Алексей Гидаспов <
> olive.c...@gmail.com
> > >
> > > > >>>>> wrote:
> > > > >>>>>>>> Dear Ignite Community!
> > > > >>>>>>>>
> > > > >>>>>>>> I suggest starting Apache Ignite 2.11 release activities.
> Also
> > > > >>>>> suggest
> > > > >>>>>>>> myself to be a release manager for this release. I plan
> > release
> > > > >>> at
> > > > >>>>> the end
> > > > >>>>>>>> of june 2021.
> > > > >>>>>>>>
> > > > >>>>>>>> ___
> > > > >>>>>>>>
> > > > >>>>>>>> Best Regards,
> > > > >>>>>>>> Alexey Gidaspov
> > > > >>>>>>>>
> > > >
> > >
> >
>

Reply via email to