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

Michael J Rubinsky mrubinsk at horde.org
Tue Apr 16 21:18:44 UTC 2013


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

> Quoting "Michael J. Rubinsky" <mrubinsk at horde.org>:
>
>> commit 70a25e2194fc5e790cebf3c18491d2a319b70395
>> Author: Michael J Rubinsky <mrubinsk at horde.org>
>> Date:   Tue Apr 16 16:54:29 2013 -0400
>>
>>    Bug: 12185 Fix bad cherry-pick.
>>
>>    Horde_ActiveSync_Device is not present in FRAMEWORK_5_0
>>
>> framework/ActiveSync/lib/Horde/ActiveSync/Connector/Importer.php |    3 +--
>> 1 files changed, 1 insertions(+), 2 deletions(-)
>>
>> http://git.horde.org/horde-git/-/commit/70a25e2194fc5e790cebf3c18491d2a319b70395
>
> My question is why are *ANY* framework commits being made to  
> FRAMEWORK_5_0 at this time.  This doesn't make sense.  Framework  
> code is not tied to 5.0 (or any other Horde version for that matter).

Sure it is. We are still doing synchronized releases for minor  
versions. I.e., new features for Horde 5.1. Bug fixes for  
functionality that exists in FRAMEWORK_5_0 are still being built from  
FRAMEWORK_5_0.

The new features in the ActiveSync code (which will be in ActiveSync  
2.4.0), while BC with Horde 5.0, still required substantial changes to  
the code base and deserve to go through the full release cycle of 5.1  
before they are declared stable.

Put another way, I'm not going to release ActiveSync 2.4.0 as stable  
before it has been more widely tested, and I'm not going to hold up  
bug fixes for the current stable code because of this.
-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 2200 bytes
Desc: PGP Public Key
URL: <http://lists.horde.org/archives/dev/attachments/20130416/3f2f0dc1/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6062 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.horde.org/archives/dev/attachments/20130416/3f2f0dc1/attachment-0001.bin>


More information about the dev mailing list