ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gintautas Grigelionis <g.grigelio...@gmail.com>
Subject Re: Ivy upcoming release - where we stand
Date Mon, 25 Sep 2017 14:59:50 GMT
I'd rather deprecate as much as possible for 2.5.0, so that deprecated
stuff could be removed in 3.0 :-)

Gintas

2017-09-25 14:51 GMT+02:00 Jan Matèrne (jhm) <apache@materne.de>:

> > I'm closing in on IVY-1420; it's Willem's patch + writeInheritedItems
> > for entire inherited configurations/dependencies blocks (and another
> > test case for that).
>
> good.
>
>
> > PR-57 breaks BC but mitigates that except for a special case. Anyway,
> > why must every release be a drop-in replacement for the previous one?
>
> It does not have to.
> With a drop-in replacement it is easier to update for the users. ;-)
> And with the upcoming 2.5.0 I would it make as easy as possible, because
> it is the first release after a long time.
>
> We could discuss major or BC-breaking changes after that. Maybe call the
> next release 3.x ...
>
>
> Jan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>

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