ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée <>
Subject Re: Ivy - any future or is it also going to be retired?
Date Wed, 07 Dec 2016 15:04:45 GMT

> Le 7 déc. 2016 à 14:43, Jaikiran Pai <> a écrit :
> +1. Nicolas' mail has some precise things that need to be done. I am willing to help
out wherever possible on those steps. I think the first thing to release probably should be
a 2.4.1-Beta-1 just to iron out any process and other issues in itself and explicitly tag
it as a beta so as to maintain the right expectations.
> One thing that I think is probably is a priority (based on what I have been trying to
attempt while helping out with Ivy patches) is that we have a central system which builds
this project and runs the testsuite regularly against a *nix and Windows system. Is this already
available in the project/Ant ecosystem somewhere? Something like a Jenkins? If not, is there
any other option we have to make sure we really release  something that is reproducible?

There is a Jenkins hosted by the ASF, and we’ve already configured jobs there.
See <>
The jobs are configured to send emails to the mailing list


> -Jaikiran
> On Wednesday 07 December 2016 05:36 PM, Oulds, Jonathan wrote:
>> Nicolas raises some great ideas,
>> I would suggest that we get those into Jira and try to cut a release from the current
code (just to test the release process).  If that works let's try to address one or two simple
to fix issues (just to give the release some value) and push out 2.4.1.
>> If there is enough interest we can start implementing some bigger features and plan
for a 2.5 release next year.
>> Jonathan Oulds
>> Snr. Software Engineer
>> McAfee
>> -----Original Message-----
>> From: Stefan Bodewig []
>> Sent: Wednesday, December 7, 2016 10:56 AM
>> To:
>> Subject: Re: Ivy - any future or is it also going to be retired?
>> On 2016-12-06, Nicolas Lalevée wrote:
>>> These are just ideas poping up my mind to show that if people are
>>> enough motivated, they can make things happen. And obviously, if
>>> things work well, credentials will be granted.
>> Yes, of course.
>>> I think this is the same for IvyDE, but it requires much more effort
>>> because the build is broken since we migrated to git, and so the
>>> release process has to be reviewed. Too much effort for me.
>> If our transition to git is causing problems we didn't foresee, we can certainly
(partially) revert it. Nobody says we need to use the same scm for all subprojects of Ant.
>> Stefan
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: For additional commands, e-mail:
>> ---------------------------------------------------------------------
>> Intel Corporation (UK) Limited
>> Registered No. 1134945 (England)
>> Registered Office: Pipers Way, Swindon SN3 1RJ
>> VAT No: 860 2173 47
>> This e-mail and any attachments may contain confidential material for
>> the sole use of the intended recipient(s). Any review or distribution
>> by others is strictly prohibited. If you are not the intended
>> recipient, please contact the sender and delete all copies.
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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