[dev] Horde release cycle

[Michael Rubinsky]

Quoting Michael M Slusarz <slusarz at horde.org>:

> It sounds like there is a plan to churn releases out on a regular  
> basis.  This is a good thing.  But I am against the idea that,  
> within a given major release for example, we are allowed absolutely  
> NO BC changes.  If something is irreparably broken, it needs to be  
> fixed.

I'm not sure I understand how we *could* make a non-BC change within a  
major release. Isn't a big point of the major number to indicate that  
the API is consistent? If a situation such as one that you are  
referring to comes up, we could always bump the major number for the  
next 6-month release. I don't think we should make any bc breaking  
changes without bumping the major version.

Also, with regards to framework packages, as far as I understood it,  
there's no reason not to break BC, and bump the major number, when  
needed - the applications can track their own dependencies via PEAR.  
Another advantage of releasing the framework libraries independently.  
My point is that if a framework library does get a bc breaking change  
(and thus a major bump), then any applications that are changed to  
work against the new library should also get a major bump...and that  
could happen at the next 6-month release, if the situation warrants it.

> If some design decision we made in the last few years turns out to  
> be untenable when put into production, it needs to be fixed sooner  
> rather than later.  I am entirely willing to sacrifice rigid API  
> stability for the flexibility needed to fix things properly.
>
> And I am still a proponent of having an application be able to  
> indicate that a particular PEAR/Horde library needs to be a certain  
> version in order to work properly.  Not sure if that is still  
> something we are considering.


> 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


mike

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