[dev] Horde 4 kickoff - dev prozess

[Michael Rubinsky]

Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Thomas Koch <thomas at koch.ro>:
>
>> thx Chuck, for clarification on the GIT layout. Maybe I may start
>> another related topic and propose a development process:
>>
>> 1. Present the Idea
>> 2. Write Requirements Document
>> 3. Write Design Specifications
>> 4. Implementation <-> (Unit) Testing
>> 5. Review
>> 6. Release
>>
>> I stress this, because I think many projects suffer from the fact that
>> coding is much more fun then planing.
>
> I'm all for having unit tests for our libraries, but in my view this  
> is way too much process. We're trying to speed up our development  
> process, not slow it down.

Agreed. A strict development cycle like this would take way too much  
time away from the limited coding time most of our developers have.


>> I think it makes sense, to be a little bit more relaxed for the
>> development process of applications and very strict with libraries. And
>> to make it easy to separate these things, it makes sense to pack them in
>> two different repositories. Checking out two or three repos to work on
>> horde is not much an issue.
>> On the other hand it would be an issue for other projects using the
>> horde libraries to checkout all applications too.

Shouldn't "other projects" be using our stable, released libraries and  
not bleeding edge HEAD code anyway?


Thanks,
mike

--
The Horde Project (www.horde.org)
mrubinsk at horde.org

"Time just hates me. That's why it made me an adult." - Josh Joplin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: PGP Digital Signature
URL: <http://lists.horde.org/archives/dev/attachments/20081021/ce3c0e34/attachment.bin>