Re: 28 Aug 2003 Commit - Horde/IMP Versions?

> 
> I'm not sure if you know how development is done for these projects, but 
> usually
> what happens is that all new development is done with HEAD.  So in 
> August 2003,
> SAM worked with CVS HEAD (from August 2003).  For release versions, 
> usually a
> new branch is made in CVS and only bug changes/fixes are made to that 
> branch
> (so that it works with released version of the Horde framework).  If a
> particular enhancement has worked fine in HEAD for some time, a 
> developer will
> sometimes take the fix and merge it from HEAD into the RELEASE branch.
> 
> 

I was under the impression this was the case, but I wanted to confirm 
it.  I know this list get pounded with silly questions and I appreciate 
you taking the time to graciously answer mine.

> 
> I don't know why you think SAM is unstable.  I'm using a version from 
> CVS HEAD
> that works just fine.
> 

It isn't SAM HEAD I am concerned with being unstable it is HORDE and IMP 
HEAD.

> 
> If you are willing to devote the time it takes to maintain and support a 
> RELEASE
> version of SAM, i'm sure the Horde developers will love for you to 
> contribute.
> Everyone is a volunteer and doing this in their own time, so I don't 
> think you
> can expect every package that they have to have a RELEASE version.
> 

I would love to contribute, but I don't want to re-invent the wheel. 
Perhaps I can assist with a RELENG version when the project branches.

At the moment, I am attempting to use Darik Horn's modified version 
dated 20030528.  I would prefer to write the amavisd_ldap driver for a 
useful version.

> 
> When CVS HEAD is relatively stable I take a snapshot and use this in my
> production environment.  If your not willing to do this you have to wait.
> 

How can you find out when Horde, IMP, and SAM HEAD are relatively 
stable?  I believe the Mozilla project calls these Milestones.  What 
would you recommend would be the latest Milestone equivalent for Horde?

> 
> This is opensource, you can do whatever you like with code, including
> contributing to the project to develop a RELEASE that works with a current
> release of Horde
> 

I would like to help further the project without re-inventing the wheel.

I really do feel that the SAM project is a worthy effort, I am simply 
frustrated with its progress over the past year.  I do appreciate the 
efforts of those who do contribute, even if their bedside manner isn't 
as good as yours.

Thank you for the detailed response.

Respectfully,


Gary


-- 
sam mailing list - Join the hunt: http://horde.org/bounties/#sam
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]