Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
From: =?UTF-8?Q?Jan_Mat=C3=A8rne_=28jhm=29?= <apache@materne.de>
To: "'Ant Developers List'" <dev@ant.apache.org>
References: <5824107d-d7bb-2b11-6615-de0fa8961bf2@gmail.com> <001e01d24ecc$f7e23e20$e7a6ba60$@de> <CALVNWHWC0LcvrbP3bz2Yw97YGiCqVK5QExKS-k3dd2KJBnmgMA@mail.gmail.com>
In-Reply-To: <CALVNWHWC0LcvrbP3bz2Yw97YGiCqVK5QExKS-k3dd2KJBnmgMA@mail.gmail.com>
Subject: AW: Ivy - any future or is it also going to be retired?
Date: Mon, 5 Dec 2016 13:46:53 +0100
Message-ID: <003601d24ef5$a7f91a40$f7eb4ec0$@de>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AdJO3dVFe2EJKcuYSzOrK1xYbKY7AAADqKRg
Content-Language: de
archived-at: Mon, 05 Dec 2016 12:47:02 -0000

> If you want to push Ivy, you need integrations with IDE.=20

Yes, I agree. But the problem getting developers to improve IvyDE.


> IMHO, IvyDE works well with Eclipse;=20

IvyDE will be available as it is. We don't delete releases as they are =
archived in the Apache archive.=20


> perhaps its [IvyDE] release cycle needs to be synced with Ivy release =
cycle (which is roughly biannual a this point).

Nice idea - but without enough developers impossible.=20


> Is there a release plan for Ivy, by the way?=20

No.


> When will this <https://issues.apache.org/jira/browse/IVY-1444> fix be =
released?

Marten has commented "it will be fixed in the next release."
So first step is getting the change into the code base. 2nd step is =
getting a release out.

I don't know the actual status of #1.
Currently there is no release planed.=20


> I don't know what a -1 (which is what I would have voted) would do in =
reality.=20

A '-1' is basically a vote 'against' the suggestion [1]. It must be =
explained so that
we could react on the arguments privded. Basically a -1 could be =
overriden by enough +1s.

If the decision requires consensus, then its called 'veto' and could not =
be overridden.
But only the removal of a committer or PMC member requires consesus [2].
                                                                       =20
[1] http://ant.apache.org/bylaws.html#Voting
[2] http://ant.apache.org/bylaws.html#Actions


> So on one hand I want that project to stay (and hope to be actively =
developed) and on=20
> the other I don't think that's going to be happen even if it isn't =
retired.

Same with us. We don't want to retire subprojects. But have to face the =
facts and get the consequences.


> Second, I'm guessing the ivy (and ant) project would very much welcome =
extra hands.=20
> So if this project is important to you, and you want a release to =
happen ...
> why don't you join the effort and help drive it.

Thanks, you're right. ;)=20


> If right now the problem is "there is noone able to create / manage =
new releases"=20
> (but some people are still around to watch over the code and fix =
bugs), maybe=20
> someone can step up specifically for the job of release manager ...

That's the plan, or the intention ;)


> Like I said in my mails, I've tried [contributing].=20
> Anyway, here's some previous mails where I tried [1] [2] [3].
> [1] http://marc.info/?l=3Dant-dev&m=3D143702067424412&w=3D2
> [2] http://marc.info/?l=3Dant-dev&m=3D143765756710466&w=3D2
> [3] http://marc.info/?l=3Dant-dev&m=3D144026083515049&w=3D2

Maybe we were sleeping some time. But we are waking up.=20
#1 was started on 2015-07-16 and a patch was merged on 2015-08-30.
#2 was started on 2015-07-23 and last response by Nicolas was that it =
breaks on Windows.
#3 was started on 2015-08-22 and last answer on 2015-08-30.=20


> Me? I can provide patches and fixes and enhancements for whatever =
little knowledge I=20
> gain by looking at existing code, but my experience with Ivy is just =
limited to the=20
> past few years when I started using it as a user.

Experience comes naturally by working with and for Ivy. So creating and =
providing patches
further. =20
With Ant I started with answering user questions on the user-list. Then =
providing some patches.


> there's really nothing to look forward to in terms of roadmap or =
releases or development.

I think the problem is that we lost most of the core developers of Ivy =
in a short timeframe.
So every development/planning stoped. (Just my personal point of view.)
Now we are trying to reactivate 'old', aquire 'new' committers and =
getting 'existing'=20
(Ant)commmiters be more familiar with the Ivy codebase, so that we could =
do more here.
(Also my personal point of view.)


Jan=20
 =20


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org