ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Policy for update third-party dependencies
Date Thu, 17 Aug 2017 00:12:09 GMT
On Wed, Aug 16, 2017 at 5:02 PM, Denis Magda <dmagda@apache.org> wrote:

> Honestly, I wouldn’t touch a dependency if it works like a charm and
> nobody requested us to migrate to a new version.
>
> Why do you need to update Apache Common coded?
>

Not sure I agree. Why not update it?


>
>
> —
> Denis
>
> > On Aug 16, 2017, at 10:36 AM, Alexey Kuznetsov <akuznetsov@apache.org>
> wrote:
> >
> > Done
> >
> > https://issues.apache.org/jira/browse/IGNITE-6090
> >
> > On Wed, Aug 16, 2017 at 8:01 PM, Dmitriy Setrakyan <
> dsetrakyan@apache.org>
> > wrote:
> >
> >> The answer is Yes, we should update. Jira ticket assigned to the next
> >> release should be enough in my view.
> >>
> >> D.
> >>
> >> On Wed, Aug 16, 2017 at 2:38 AM, Alexey Kuznetsov <
> akuznetsov@apache.org>
> >> wrote:
> >>
> >>> Hi, All!
> >>>
> >>> Do we have any policy for updating third-party dependencies?
> >>>
> >>> For example, I found that we are using very old  Apache Common codec
> >> v.1.6
> >>> (released in 2011)
> >>> And latest is Apache Common codec v.1.10
> >>>
> >>> Do we need to update to new versions from time to time?
> >>> And how?
> >>>
> >>> Just create JIRA issue, update pom.xml and run all tests on TC - will
> be
> >>> enough?
> >>>
> >>> --
> >>> Alexey Kuznetsov
> >>>
> >>
> >
> >
> >
> > --
> > Alexey Kuznetsov
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message