ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Lalevée <nicolas.lale...@hibnet.org>
Subject Re: Ivy release schedule
Date Mon, 13 Jan 2014 22:52:13 GMT

Le 4 janv. 2014 à 14:11, Nicolas Lalevée <nicolas.lalevee@hibnet.org> a écrit :

> 
> Le 2 janv. 2014 à 17:34, Nicolas Lalevée <nicolas.lalevee@hibnet.org> a écrit
:
> 
>> 
>> Le 2 janv. 2014 à 17:10, Charles Duffy <charles@dyfis.net> a écrit :
>> 
>>> Absolutely, then. :)
>>> 
>>> I was under the impression that only members of the PMC could call a vote
>>> for a release.
>> 
>> Here is the official rules:
>> http://ant.apache.org/bylaws.html
>> 
>> You can do a release, but it will be officially accepted only by a majority of the
PMC.
>> 
>>> If that's something any committer can do, I'll gladly run the process after
>>> your pending feature is in.
>> 
>> I think we have a good doc about how to release:
>> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html
>> 
>> I willing to help, especially for the optional publication to the Eclipse updatesite.
>> 
>> I'll keep you posted about my progress.
> 
> I nailed it. It needs a little bit of documentation thought. I'll write some soon.

doc written. It's good for me.

Nicolas

> 
> Nicolas
> 
>> 
>> Cheers,
>> Nicolas
>> 
>>> 
>>> Thanks!
>>> 
>>> 
>>> On Thu, Jan 2, 2014 at 10:02 AM, Nicolas Lalevée <nicolas.lalevee@hibnet.org
>>>> wrote:
>>> 
>>>> 
>>>> Le 30 déc. 2013 à 19:35, Charles Duffy <charles@dyfis.net> a écrit
:
>>>> 
>>>>> Howdy, all --
>>>>> 
>>>>> There's rather a lot of good stuff on Ivy's trunk.
>>>> 
>>>> Agreed.
>>>> 
>>>>> Any thoughts as to when
>>>>> we might be in a position to start a release candidate series?
>>>> 
>>>> I think any time a committer is willing to do so.
>>>> 
>>>>> (As there are tickets assigned to 2.4.0, and nothing on 2.3.1, would
I be
>>>>> correct in gathering that that's where we're going next?)
>>>> 
>>>> Yep 2.4.0 should be the next one.
>>>> 
>>>> I only have one wish. I am working on supporting "packed" (.pack.gz)
>>>> resources from Eclipse update sites. For that I would need to redesign a
>>>> feature which is only in trunk: uncompress artifact on resolve (not
>>>> documented yet, see DefaultRepositoryCacheManager#uncompressArtifact).
>>>> Since I would like to break it a little bit, I would like to do it before
>>>> releasing it, so no backward compatibility have to be supported.
>>>> I am struggling a little bit with it, but I don't think it will take very
>>>> long.
>>>> 
>>>> Nicolas
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>> 
>>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
> 


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


Mime
View raw message