[dev] Horde 5?

[Gunnar Wrobel]

Zitat von Michael M Slusarz <slusarz at horde.org>:

> Quoting Gunnar Wrobel <wrobel at horde.org>:
>
>> Zitat von Ralf Lang <lang at b1-systems.de>:
>>
>>>>> I think we began changing the Wiki page to "Horde 4.1 not planned"
>>>>> before it went into maint.
>>>>
>>>> I would love to start breaking BC and removing deprecated stuff, since
>>>> it seemed like half of the work/fixes I did this evening was figuring
>>>> out how to keep compatibility rather than fixing the problem.
>>>>
>>>> But I also think before we start work on Horde 5 we should probably
>>>> decide on how (or if) to setup the git repo differently than what we
>>>> currently have. Meaning: separate git repos for each
>>>> application/framework going forward?
>>>
>>> Don't know if we shouldn't postpone this repo reorg to release time.
>>
>> If somehow possible I would say we should definitely postpone this.
>>
>> Michael, do you see serious issues ahead in case we don't  
>> reorganize the repo before the next release?
>>
>> Not that I wouldn't like to break up the repo. I said so before and  
>> if we are actually considering this I'm really happy. I'll  
>> definitely invest my part in ensuring that we have the tools ready  
>> to allow working based on a splitted repository. Might mean I will  
>> take a closer look at "composer" which could help.
>
> My personal experience recently has been that I am spending as much  
> (if not more) time dealing with branch management than with items  
> like fixing bugs or adding new features.  As far as developer  
> efficiency is concerned, this is a major issue, and one I would  
> rather address sooner than later.  But I realize I may be in the  
> minority here.

At the moment I guess we'd still need to discuss how much splitting we  
actually want. I would like to go for one repo per application and one  
repo for every framework package. If I remember correctly others were  
completely against the split or wanted to keep the framework in a  
monolithic block.

This decision probably already includes a number of technical details  
and issues to consider. I know that I didn't wrap my head around the  
topic completely yet and I would assume that I'm still missing more  
than half of the things that splitting the repo would actually affect.

At the moment I assume however that we could do it package by package  
anyhow. Why not experimentally copy IMP into its own repo and see what  
this would entail and what this would mean for building packages from  
it?

Gunnar

>
> michael
>
> ___________________________________
> Michael Slusarz [slusarz at horde.org]
>
> -- 
> Horde developers mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org

-- 
Core Developer
The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de