Re: Release 2.1

Am 27.01.13 14:15, schrieb Rudolf Korhummel:
> Hi Lenya Devs,
>
> Does it mean that we have to remove all binary libraries before we can
> do the new release ?
> If yes:  Would it be good to use maven instead of ant ?

This shouldn't be necessary, we could as well use Ivy (which can access 
Maven repositories) for dependency management.

Having worked with Maven for a couple of years now, I'm not a particular 
fan of it. The syntax is overly verbose, some concepts are very complex 
(e.g. profiles) and the build process is very restrictive.

I don't think it is necessary or particularly beneficial to move away 
from Ant for the existing codebase. If we decide to do this, though, we 
might want to take a look at Gradle and maybe Buildr (Gradle seems to be 
more stable, Buildr otoh is an Apache project).

-- Andreas


> I'm not familiar with maven, but it seems to that it will take some time
> to do it.
> If we want to release soon, I think it would be good if we can move this
> step to a later release.
>
> WDYT
>
> Rudolf
>
>
>> On 12/16/2012 08:42 AM, Rudolf Korhummel wrote:
>>> Hi Lenya Devs,
>>>
>>> I would like to start a discussion about the possibility to release 2.1
>>>
>>> Our last release was about 20 month ago and the activity in the
>>> community is low so a new release in the near future would be a good
>>> thing to reactivate the project.
>>>
>>> From MPOV we don't need much new features , but a new state of the art
>>> design of the default publication would be necessary. It might also be
>>> useful to have a simple publication which can be used by new users  to
>>> build there publications on top.
>>>
>>> WDYT ?
>>>
>>> Are there some devs around who can help ? I think I will have time after
>>> christmas to work on this.
>>>
>>> Best
>>> Rudolf
>>>
>>
>> There's been quite a bit of discussion about releases recently. I'd
>> have to do some digging to find out which list it was on: infra,
>> board, or members. Basically it came down to that source releases
>> shouldn't include binaries in them, at least not binary libraries. Our
>> releases contain all of those libraries, so it would go against that.
>> I'll have to spend some time tracking down what the decision was.
>> Using something like Maven obviously removes that problem.
>>
>> Richard
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>