[dev] [commits] Horde branch FRAMEWORK_5_0 updated. 450bba25ab112a31ff062869971d780fd011f8f5

[Michael M Slusarz]

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

> For example, I should (and want to) be able to release IMP 5.1 to  
> work with Horde_Imap_Client 3.0.  But there is no need to force, for  
> example, Horde 5.1 to use 3.0.  These are perfectly valid  
> development decisions and sort of the whole reason why we are using  
> PEAR packaging.  Will this setup work running directly out of the  
> git repo?  No.  That **SHOULD** be irrelevant.  The fact that it  
> isn't proves that our current repository setup is wrong - we are  
> being limited in what we can do by artificial boundaries.

Probably would be better if I put it this way:

* I agree that we should be able to maintain different "branches" of  
framework packages.
* However, this is not practical under our current repo layout.
* Using FRAMEWORK_5_0 branch as a proxy for the inability to do the  
above is simply incorrect.  This is nothing more than trying to fit a  
square peg in a round hole.  It is a blatant disregard for the  
separation of framework libraries and application code.
* If we need to maintain separate framework package versions at this  
time, we must create a topic branch.
* All of the above becomes moot once we move packages to separate VCS repos.

Additionally, I would add as my opinion:

* If we are truly uncertain about changes to a package working in  
previous application versions, by definition these are not BC changes  
and we need to bump the package version number.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]