[dev] Horde release cycle

[Chuck Hagenbuch]

Quoting Michael Rubinsky <mrubinsk at horde.org>:

> 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.

Exactly. If a major release is flawed, it doesn't have to last more  
than 6 months.

-chuck