Re: [commits] Horde branch FRAMEWORK_5_2 created. 05cb8e07a0df57801bd06eb48c2ddc906b2064b9

Michael J Rubinsky <[email protected]>
Newsgroups gmane.comp.horde.devel
Message-ID <20140605121735.Horde.01JxubLzcfiDxhHndt2LZA1@h4.theupstairsroom.com>
Quoting Jan Schneider <[email protected]>

>
> Zitat von Michael J Rubinsky <[email protected]>:
>
>> Quoting Jan Schneider <[email protected]>
>>
>>>
>>> Zitat von Jan Schneider <[email protected]>:
>>>
>>>> The branch "FRAMEWORK_5_2" has been created.
>>>>      at  05cb8e07a0df57801bd06eb48c2ddc906b2064b9 (commit)
>>>
>>> All bug fixes, and only bug fixes for the Horde 5.2 app releases  
>>> go into this branch. Bug fixes for libraries go into master.  
>>> master is also open for new development again.
>>> We target the repo split for after the final app releases.
>>>
>>> -- 
>>> Jan Schneider
>>> The Horde Project
>>> http://www.horde.org/
>>> https://www.facebook.com/hordeproject
>>>
>>> -- 
>>> dev mailing list
>>> Frequently Asked Questions: http://wiki.horde.org/FAQ
>>> To unsubscribe, mail: [email protected]
>>>
>> Are we/can we target the next non-bugfix release to be H6? 
>
> If there are good reasons for it, sure. Reasons I can see myself is  
> solving the TODOs that require BC breaks, or switching to namespaces.
>
> -- 
> Jan Schneider
> The Horde Project
> http://www.horde.org/
> https://www.facebook.com/hordeproject
>
> -- 
> dev mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: [email protected]
Exactly.  I've got a bunch of todos in ActiveSync that could benefit  
from breaking BC. Also namepaces would be a good argument for this as  
well. So,  basically count me as a +1 :) 


mike 
Sent from mobile 

-------- Original message --------
From: Jan Schneider <[email protected]>
Date:06/05/2014  12:11 PM  (GMT-05:00)
To: [email protected]
Subject: Re: [dev] [commits] Horde branch FRAMEWORK_5_2 created.  
05cb8e07a0df57801bd06eb48c2ddc906b2064b9



-- 
dev mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.