On Mar 6, 2012, at 8:53 PM, Klaas Freitag wrote: > On 06.03.2012 20:31, Georg Ehrke wrote: > Hi, > >> I would guess Frank is a bit overworked due to the cebit :( > Hmmm ;-) > >> This is a really difficult question about fixing bugs or keeping up >> compatibility. > Yes, and its a question of what and how many versions we can and want to > maintain. > > One option would be to ask upstream at SabreDAV why they went to 5.3 and in > which areas of SabreDAV 5.3 features are used. Maybe it is possible to do a > SabreDAV 1.6 backport to 5.2 for our usecases. But honestly I don't think > thats a good idea, as I think that the SabreDAV guys also thought about that > and have good reasons to go for 5.3. And we don't want to maintain a SabreDAV > branch ourselfes, never ever.
Frankly I didn't want to bother maintaining PHP 5.2. Doing so takes more time, and even PHP 5.2 itself isn't maintained anymore. SabreDAV is a full-time project for me, and from all the things I wanted to do, keeping in check with old dependencies was not one of them. It's also a statement. If you are on a host that refuses to upgrade to PHP 5.3, it may be time to look for something else :) Perhaps something like a VPS where you do have full control. Some of the stuff I'm using from PHP 5.3 are closures, and a bunch of the new DateTime features. In the future, I will also move to using namespaces. There's more to it than just not using PHP 5.3 features, I also want to guarantee a certain quality level. This is a lot harder to do with outdated software. > > So my opinion is: We have to carefully limit the number of ownClouds we have > to maintain. As a result we should go the hard way and also require 5.3 for > ownCloud 4. 5.2 users have to stay with ownCloud 3. > If we feel that is too hard for the users, we would have to ship oC4 with > the old SabreDAV version and still go with 5.2. In that case we should > announce *now* that oC5 will require 5.3. For that it would be interesting to > know which of our known bugs the 1.6 update really fixes. > > I think the most critical thing here is communication and clear statements to > allow users to plan: > - When will we release which oC version? > - Which version of PHP will we require when? > - How long do we support which oC version? > - What does this support mean from the upstream community. > > regards, > Klaas > >> >> >> Am 04.03.2012 20:15, schrieb Jakob Sack: >>> Hi, >>> >>> when I integrated SabreDAV in ownCloud I accidentally dropped PHP <5.2 >>> support. Of course PHP 5.3 is two and a half years old but that does >>> not necessarily mean that every webspace provides PHP 5.3. >>> Frank, do you you think? Of course I'd favour depending on PHP 5.3 but >>> on the other hand I remember well that ownCloud should run everywhere. >>> Regards, >>> >>> Jakob >>> >>> Am 04.03.2012 19:52, schrieb Stephan Schulz: >>>> Hi everyone, >>>> >>>> in my opinion, fixing (those) bugs should be priority no one. I guess >>>> most people can control their PHP installation or at least ask for an >>>> update. If not they still have the option to stay with owncloud 3 for >>>> some more time. >>>> >>>> Stephan >>>> >>>> ------------------------- >>>> >>>>> On 3 March 2012 21:41, Christophe <[email protected] [3]> wrote: >>>>> >>>>>> Hi everyone, >>>>>> >>>>>> I would strongly prefer SabreDAV 1.6 over PHP 5.2 support, though >>>>>> you can't argue with security support. RHEL 5 still supports PHP >>>>>> 5.1.6(!) and Ubuntu 8.04 comes with PHP 5.2.4. (: >>>>>> >>>>>> Christophe >>>>>> >>>>>> _______________________________________________ >>>>>> Owncloud mailing list >>>>>> [email protected] [1] >>>>>> https://mail.kde.org/mailman/listinfo/owncloud [2] >>>>> >>>>> Don't forget that most ISPs have lots of clients with legacy code, >>>>> and cannot update to php 5.3 yet. >>>>> >>>>> It will take some time before we can be php 5.2 free. >>>>> >>>>> Owncloud should adopt moodle view, and have php 5.2 and php 5.3 >>>>> versions. >>>>> >>>>> My 0.2 cents >>>>> >>>>> Mauro Vale >>>>> > > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
