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: [CANCELED][VOTE] Release Ivy 2.4.0
Date Sat, 13 Dec 2014 15:54:55 GMT
I pushed the current style folder into git so we can go forward with the release. If we have
a better process later, we will just change it.

Nicolas

> Le 10 déc. 2014 à 10:57, Nicolas Lalevée <nicolas.lalevee@hibnet.org> a écrit
:
> 
> Note that the style files are also useful to edit the doc within Ivy’s code source.
So this needs to be easily fetchable for contributors.
> 
> Having to maintain the styles folders between the source and the site one doesn’t seem
that a burden. I prefer to have the burden on committers than on contributors.
> 
> Nicolas
> 
>> Le 10 déc. 2014 à 09:28, Jan Matèrne (jhm) <apache@materne.de> a écrit
:
>> 
>> Security hint: 'pushing' is not as secure as 'polling' here ... Maybe
>> passwords have to be configured...
>> 
>> Jan
>> 
>>> -----Ursprüngliche Nachricht-----
>>> Von: Jan Matèrne (jhm) [mailto:apache@materne.de]
>>> Gesendet: Mittwoch, 10. Dezember 2014 07:57
>>> An: 'Ant Developers List'
>>> Betreff: AW: [CANCELED][VOTE] Release Ivy 2.4.0
>>> 
>>>> The ideal solutions to all this headaches would probably to have
>>>> everything
>>> in >git (including ivy's website), unfortunatly as far as i know we
>>> can't publish >website via git @ASF for the moment. Infra offers a
>>> gitpubsub feature but i >read somewhere that we can't use it to publish
>>> websites.
>>> 
>>> Would a Jenkins job help here?
>>> It could build the website from git and 'push' (not git push ;) it
>>> somewhere.
>>> 
>>> 
>>> Jan
>>> 
>>> 
>>> 
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Antoine Levy Lambert [mailto:antoine@gmx.de]
>>>> Gesendet: Mittwoch, 10. Dezember 2014 01:18
>>>> An: Ant Developers List
>>>> Betreff: Re: [CANCELED][VOTE] Release Ivy 2.4.0
>>>> 
>>>> Yes !!!
>>>> 
>>>> Antoine
>>>> On Dec 9, 2014, at 9:36 AM, Stefan Bodewig <bodewig@apache.org>
>>> wrote:
>>>> 
>>>>> On 2014-12-09, Jean-Louis Boudart wrote:
>>>>> 
>>>>>> This directory containing styles (css,etc...) is used by both
>>>> website
>>>>>> (which is still in svn and published via svnpubsub) and project
>>>>>> documentation (which is in ivy's git repository). As infra was
>>>>>> proposing git-svn mirror it was a good compromise. Website could
>>>> live
>>>>>> using svn:externals to fetch appropriate files, and project
>>>>>> documentation could use git submodules.
>>>>> 
>>>>>> Considering we're talking about a few files that doesn't move too
>>>>>> often i was suggesting duplicating them by hand and/or automating
>>>>>> it via a script during the release process.
>>>>> 
>>>>> OK, I think I understand.  If this is really only needed for a
>>>> release
>>>>> build, having the build process fetch them from svn (which I think
>>>> you
>>>>> are suggesting) seems to be a good choice.
>>>>> 
>>>>> Stefan
>>>>> 
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> 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
> 


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


Mime
View raw message