[PHP-DEV] Re: Design by Contract
On 2015-02-05, Dmitry Stogov dmi...@zend.com wrote:
--001a11c20e52da1ee0050e556679
Content-Type: text/plain; charset=UTF-8
Hi Yasuo,
Following our conversation, I tried to imagine how DbC should look like in
PHP from user perspective. Finally, I was influenced by the semantic
proposed in D, and syntax proposed for Java. So, these are my initial
thoughts:
For php it may look like the following:
function foo()
requre(input-assert-expression)
ensure(output-assert-expression)
{
...
}
It would require only one new reserved word ensure.
The assert expressions may be checked or not depending on ini directive.
It should be also possible to prevent code generation for assertions (zero
cost asserts). It was already implemented for
https://wiki.php.net/rfc/expectations
I really like the idea. D allows complete blocks that then use assert. Might
be worht investigating why they went for a block rather than one expression.
For inherited methods, only the self input-assert-expression should be
checked, and all parent output-asser-expression. This is borrowed from D
but not necessary to be repeated exactly.
I think we shouldn't introduce invariant constraints for classes now. May
be later.
I believe invariant is one of the strongest contract ideas as it goes well with
proper encapsluation and immutability like structures.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHPDBG nonsense (Was: Re: [PHP-CVS] com php-src: Made phpdbg compatible with new engine: ...)
On 2014-10-26, Bob Weinand bobw...@hotmail.com wrote: Am 26.10.2014 um 17:23 schrieb Lester Caine les...@lsces.co.uk: On 26/10/14 15:41, Bob Weinand wrote: Ask them at PhpStorm. They were pleased to not have to use DBGp for it. They just initially requested it because they didn’t knew any better protocol. That’s all. PHPStorm like PHP-FIG have their own agendas which do not play well with other groups of developers. Just because one thinks an idea is good does not mean that everybody else has to adopt it. So what becomes 'main stream' has to have common consensus and the voting rules provide that. When was the vote on this rework taken? -- Lester Caine - G8HFL - Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk There wasn’t any vote and there won’t. /dev/null likes to listen to your complaints why we should have voted on it. step back a bit here, stay professional, there is no need for passive aggressiveness. But now it’s in, let’s rather try to improve what’s there than screaming for a vote - it won’t help anyone and hinder possible work on improving the current thing. From what I see, the complan is about the initial protocol and not about how to improve it or not. This whole protocol business needed an RFC, which I haven't seen. So we should come up with a good way of deciding which protocol to use and how to implement it. Before this, I would strongly vote to not incldue the current verison in PHP 7 at all. Also let me point out that the code belogns to everyone and everyone will have to deal with it so we better make an informed decision now. Thanks -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Let's make a 5.7 release
On 2014-08-15, Ferenc Kovacs tyr...@gmail.com wrote: --001a11c1258a38c82a0500a8b070 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable we don't have a single instance where we were able to deliver a minor release under a year, and I'm fairly sure that 7.0 will see more proposed features/changes as any previous minor, because there are stuff which can only happen in a major version. More changes(both in numbers and in impact) will need more time to stabilize, so I think that the one year roadmap for 7.0 is unrealistic. You seem to be arguing that 5.7 would pull away resources from 7.0, but I'm fairly sure that 5.7 would be the smallest of the 5.x minor versions for two reasons: we are getting better with not letting BC breaks slip in in minors plus working on a major version is much more interesting as you have less restrictions, so I think that 5.7 will/would be only to make the bed for 7.0, mostly introducing E_DEPRECATEDs and maybe a handfull of small features. I think that there is no reason to give up our current release policy and roadmap, and bet everything on PHP7, we don't lose anything with keeping 5.7. My main concern with this is that it's php6 all over again. A PHP 7 where everyone waits and pushes all their new stuff in their but nobody actually ever releases because one more feature or they are too busy maintaining the old series. I personally feel PHP7 will be stale and slowly die if we do a 5.7, or who wants to even further support multiple branches with different APIs (didn't we learn anything from PHP 6?). -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Let's make a 5.7 release
On 2014-08-15, Pierre Joye pierre@gmail.com wrote: --001a1133979e094b370500b2c0a9 Content-Type: text/plain; charset=UTF-8 On Aug 16, 2014 12:20 AM, David Soria Parra d...@php.net wrote: (didn't we learn anything from PHP 6?). I did. And with opcache. Both with hypothetical deadlines based on arbitrary random facts about the status or stability. Here we have two issues, whether or not we need a 5.x to prepare 7 and if one year Dev time is enough. Let be realistic instead of yet again trying to achieve impossible goals, or think we achieved them and release something we won't be able to change for the next decade. Let me summerize a few things that have come up: (1) phpng doesn't justify PHP7 It does. It's a complete new engine. It has performance improvements. Where do you draw the line of what justifies a PHP 7? It's a major BC break and we needd a major version for it (2) We can't get it stable. That's to be debated. The question is, with what we have now can we stabelize that? Modern release process try to minimize the delta between versions as much as possible. The only reason why we do a 7 instead of 5.7 is becuse we have a BC break to serve. In fact we do want to serve it as soon as possible. That we ensure people have time to move their products over. Most importantly we keep have to keep the divergance between branches as small as possible to make moving to new versions easier for our users and easier for us to maintain all the open branches (which are too many already). So the only question remains: Can we do PHP 7 with exactly ONLY the features we have in the next 12 months? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] [VOTE] Mutliple defaults in switch statements
On 2014-08-12, Sara Golemon poll...@php.net wrote: On Tue, Aug 12, 2014 at 10:08 AM, Andrea Faulds a...@ajf.me wrote: On 12 Aug 2014, at 17:53, Sara Golemon poll...@php.net wrote: Voting is open: https://wiki.php.net/rfc/switch.default.multiple#vote I’m all for this, but the *minimum* discussion period is *two* weeks. The two-week period is advisory and we don't need to get hung up on process for the sake of process. There's been no meaningful discussion in the past week because nobody thinks this is remotely a bad idea. Hell, some have questioned why this was put into an RFC in the first place. (It's arguably a bug, since the existing behavior could never have been described as right or intentional). If you're so worried about violating RFC process, I can revoke it entirely and just commit it without voting, and I'd be completely in the right. Or, we can apply a reasonable amount of process without getting hung up on seven days worth of... no discussion whatsoever. -Sara I agree with Sara here. The process if for human and not for it's own sake. Trivial and non-controversial changes like this really don't need the nitpicking which is going on. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Thoughts on C version supported for PHP-Next
On 2014-07-25, Andrea Faulds a...@ajf.me wrote: On 25 Jul 2014, at 18:02, Nikita Popov nikita@gmail.com wrote: I think the main question here is whether MSVC will have good C99 support by the time PHP-Next is released. The other major compilers (GCC, Clang, Intel) may not support all of C99 (esp stuff like FP pragmas), but have a reasonable degree of support. If we can, I'd be very much in favor of using C99. In particular mixed code+declarations is a major code quality improvement to me. Well, we don’t need to allow all of C99. We can simply allow using features that are widely supported and actually useful. For example, declarations between statements, and C++-style line comments with //. Though for consistency with the rest of the codebase, perhaps we should stick to C-style /* */ comments. It is hard to judge what widely supported means. PHP is so widespread that people run it on embedded systems, 10+ year old servers (see old masters.php.net) and compile them with compiler most of us have never touched (suncc, pcc). I think we have to come up with good arguments for C99 support that we just can't do with C89 in order to potentially keep out people. tl;dr: I believe unless we have strong arguments we should acknowkledge that PHP is so widespread that changing compiler can make some users unhappy and if we don't have really good reasons we shouldn't. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RFC: Move phpng to master
On 2014-07-21, Michael Wallner m...@php.net wrote: --001a11345984e013cd04feb0d9a1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 21 Jul 2014 10:21, Julien Pauli jpa...@php.net wrote: PHP-Next. I don't think that a cleanup is nearly as important as php-ng is as we stand currently. The will be no mercy from the competition. We can start reworking the API when it hit master. --001a11345984e013cd04feb0d9a1-- I want to remind that the last attempt of PHP 6 died because it was mostly unmaintained as master for a long time and we continued to postpone it. We should try to not again make a big move but take babysteps and focus on phpng and 64bit as the major features and not maintain a branch while we are doing 5.7. This will undoubtful lead to a similar abundance of the master branch as we just don't have the ressources to maintain more branches (a point already made when we discussed the release plan). I think we should consider steps to make phpng the major development branch within the year and if stabelizing it within the year possible, make it the next release. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RFC: Move phpng to master
Am 7/21/14, 10:21 PM, schrieb Yasuo Ohgaki: Even if we have PHP-5.7 branch, we have merge up policy. Therefore, any new feature will end up with master, I suppose. If a new feature is only available to PHP-5.7 branch, it's a merge bug, isn't it? Regards, We had this policy before and it didn't help us. The problem is maintiaining all the branches and keeping people interested in the next branch because people tend to focus on the currently release branch. When we decided upon the release RFC we talked a lot about the overhead of maintaing multiple branches and tried to reduce the amount of branches. In particular with API changes it becomes tidious if we try to maintain a feature across branches and that implicit divergence has to be resolved better sooner or later, or otherwise it would be just like the old php6 again. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RFC: Anonymous Classes
Lazare Inepologlou linep...@gmail.com schrieb: I use anonymous classes very frequently in Java and in C#, and I would say that they are quite useful. However the examples given in the RFC are really bad ones. Why on earth would you need a constructor for an anonymous class? Anonymous classes are used to implement quickly some interface. Frankly, constructors are not part of any interface. Besides a constructor is totally useless in an anonymous class as it will never be called after the object is created. The need for anonymous classes in Java mostly comes from implementing interfaces on demand due to the lack of lamdas and the requirements of a strongly typed language. PHP has lambdas and it doesn't require you to match typing. Therefore I think the preferred way for most of the use cases is to use a lambda or if a bigger implementation is necessary, to give it a name. Due to namespacing you don't pollute the global scope anyway. Therefore I don't see much reason left as to why add anonymous classes and I really have a hard time finding a use case, except for trying to write PHP as you would write Java (which most likely is a bad idea). - David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Question on XMLReader
John Stokes jsto...@heartofthefyre.us schrieb: I'm working on documenting the XMLReader and XMLWriter classes. Is there someone on the list that can answer some questions about the details of how XMLReader works? Please don't ask to ask. Sent a mail to this list or to the php.doc mailinglist and just ask your question. Thank you ps.: yes there will be people that can answer questions regarding those two classes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Call for participation: github pull request
We have recenty discussed a lot of new language features and RFC while our github pull requests are continously growing without getting pulled. We have 74 open pull request. So this is a clal for participation in helping to wingle those numbers down. If you have karma and can review open changes please feel free to merge them. It's very unfortune that we have so many open patches not processed. - David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Wake up
Florin Patan florinpa...@gmail.com schrieb: - lack of clear documentation about the internals: you really can't tell me that the docs out there are clear because I did a bunch of searching for them and I'm pretty good at finding stuff You are welcome to improve the documentation and make it easier for people to get into internals. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Pull requests report (27/8/2013)
On 2013-08-27, Lior Kaplan lio...@zend.com wrote: --089e01175f31fb193804e4f1a4bf Content-Type: text/plain; charset=UTF-8 Hi, I'm please to say that we keep processing the requests faster and faster, leaving only few not handled in their first week. Thanks for everyone who helped. Again thanks for this. They are helpful. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Moving PHP documentation to Git repository
On 2013-06-25, Ferenc Kovacs tyr...@gmail.com wrote: there were some initial discussion and work done on moving the docs to git, see https://wiki.php.net/doc/git http://git.php.net/?p=3Dweb/doc-editor.git;a=3Dshortlog;h=3Drefs/heads/GIT_= READY http://marc.info/?l=3Dphpdocm=3D132321958514090w=3D2 but it seems that we lost momentum, but I think that this isn't a technical problem, just lack of interest (svn and the online editor just works for the regulars), maybe others have different opinions on this. and I'm fairly certain that the slow integration of the patches also not a technical problem as well. I think that it would worth more to figure out and fix the underlying problem which causes the current delay for integrating the incoming patches= . moving to git/github without fixining the underlying issue would only mean that we switched to pull requests not getting accepted in a timely manner(which is unfortunately common with our other git/github repos). generally speaking i am in favor in moving more and more to git. we lost momentum and I am stuck with a new job and RMing. I can help with technical questions but don't hav emuch time implementing it. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: About to end 5.3
On 2013-06-19, Johannes Schl�ter johan...@php.net wrote: Hi, As the release of PHP 5.5.0 is imminent it is time to implement the decision about PHP 5.3's EOL. In https://wiki.php.net/rfc/php53eol it was decided that PHP 5.3 should go into security only mode once PHP 5.5 was released. As PHP 5.3.27 has been branched of and is aimed for release in two weeks time (5.3.27RC1 tomorrow) this will be after 5.5.0 and therefore the last regular PHP 5.3 release. Currently there is no plan to release 5.3.28 so the PHP-5.3 BRANCH IS CLOSED NOW. we have to announce this on the frontpage of php.net. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: About to end 5.3
On 2013-06-19, Johannes Schl�ter johan...@php.net wrote: Good bye 5.3, you were a great step for PHP! Looking forward to a bright and open future! Thank you for taking care of this branch for so long. Keep the good job up. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] About fileinfo test.mp3
Hi Anatol, I saw your commit 74555e7c26b2c61bb8e67b7d6a6f4d2b8eb3a5f3 added a 4mb mp3 file. Is it possible to create a much smaller mp3 that helps to reproduce the same bug? The file blows up the taball file for the final release, which I hope to keep as small as possible. Thanks in advance, David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: php-fpm and systemd integration
On 2013-05-17, Remi Collet r...@fedoraproject.org wrote: --030306010103010609050002 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, I plan to allow php-fpm to be aware of systemd and so, use the type=notify mode. I'd like to apply to attached patch to 5.4 and 5.5, as this change have no impact on standard build (need new --with-fpm-systemd build option). Any feedback before I process ? I saw you already comitted this. As mentioned before, new features belong to master and not to PHP 5.5.0 which is in RC phase. Therefore I think this feature shouldnot be added to 5.5.0. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: [PHP-CVS] com php-src: Remove curl wrappers: ext/curl/config.m4 ext/curl/config.w32 ext/curl/interface.c ext/curl/php_curl.h ext/curl/streams.c ext/standard/basic_functions.c
On 2013-04-25, Stas Malyshev smalys...@sugarcrm.com wrote: Hi! Shouldn't we Keep CURL_WRAPPERS_ENABLED defined to 0 ? or remove it from PHP-5.4 before 5.4.15 ? (was not included in any official version yet) Since the wrappers are gone, I think we should just drop it. If I don't hear any objections and nobody beats me to it, I'll do it this weekend. Since it's a revert, I think it's OK to do it in the RC branch too. Yes please go ahead and revert it. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] ext/standard/tests/array/array_column_object_cast.phpt failing
Hi Sarah, Hi Ben, ext/standard/tests/array/array_column_object_cast.phpt is failing on PHP-5.5. I bisected to: 1a03bd5dee97a0f8b9e74b7f8db5231abd8cc7e4 is the first bad commit commit 1a03bd5dee97a0f8b9e74b7f8db5231abd8cc7e4 Author: Sara Golemon poll...@php.net Date: Mon Apr 22 14:57:05 2013 -0700 Allow array_column() to take -1 as a valid value in third param Also do some cleanup and simplification to make this code more readable in the long term. Please have a look and run the test next time before you push. Thanks, David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [VOTE] Removal of curl-wrappers
On 2013-04-17, Pierrick Charron pierr...@adoy.net wrote: --001a11c37cdc78c2e304da95cfde Content-Type: text/plain; charset=ISO-8859-1 Hi folks, I just opened a vote for the curl-wrappers removal in 5.5. Since we are in a tight schedule, the vote duration will only be a week and will end April 24th. You can vote there : https://wiki.php.net/rfc/curl-wrappers-removal-rfc#vote As a friendly reminder. I tag beta4 on Wednesday around 10:00 UTC. Is this getting into before or not? David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Add a constant to reflect --with-curlwrappers
On 2013-04-12, Johannes Schl�ter johan...@schlueters.de wrote: 5.3 users might depend on some part of the behavior and have learned to live with bugs. We shouldn't kick features at this stage. curlwrappers should definatly stay in 5.3 and 5.4. I have no problem with having them removed in 5.5 (with an RFC) but I prefer to have it done before beta4 as this is going to be our last beta. Removing it in RC phase would bend the meaning of stages in the release process even more. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: libmagic 5.14 upgrade
On 03/26/2013 11:44 PM, Anatol Belski wrote: What +/- I personally see upgrading this at this time: contra: - there might be bugs, the next release might have not all them fixed - 5.11 is what the latest linux exts have even as dev - older/custom magic files might be incompatible pro: - latest libmagic data - better safety for the future - in a year all that libs are for sure upgraded in the main distros - further upgrades can be better handled HI Anatol, thanks for putting this patch together. However as we already reached feature freeze and we are will have beta2 tomorrow I think it's a bit too late for so much new code. I cannot really judge the sideeffects of this upgrade and would prefer to be strict about the feature freeze. So please do not update the library unless Stas decides that he wants to do it in 5.4, in that case I have to go with his decision. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: PHP 5.5 and clang
On 2013-03-26, Ond?ej Sur? ond...@sury.org wrote: --bcaec548a7f385895a04d8d51fce Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I am trying to build PHP 5.5beta1 with clang, so the question is: Would you be interested in the results? This would be one shot only. Hi Ondrey, yes I would be very interested in these results. I personally build PHP with clang most of the time and think we should use it's features to provide better analytics. Also I think since freebsd switched to clang ,we should ensure that PHP can be compiled with clang. Thank you very much for your work, David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: libmagic 5.14 upgrade
On 03/27/2013 09:35 PM, Pierre Joye wrote: We have done that many times in the past for 5.3 and 5.4. It is relatively risk free. Even more for 5.5 during beta phase. It does not add new features but fixes bugs. The good side effect is that we can test it well with 5.5 and back port to 5.3/4 later. I consider it a feature and not a necessary bugfix. In addition anatoly is saying that there are still problems with the patch. Both are reasons for me to believe that upgrading it 1-1.5 month before a final is not worth the risk. I would prefer to be more strict about the feature freeze than we were with 5.3 and 5.4. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Enable Zend OPCache by default in php.ini-development during beta phase?
Hi Internals, I added the default Zend OPCache settings to php.ini-development and php.ini-production atm. To have more people testing the opcache I would like to enable the OPCache in php.ini-development during the beta phase and disable it once we start the first RC. I hope we catch more errors with standard applications. As betas should not be used in production I think we won't have much problems with temporarly enable it. In case there are no objections I will commit this before beta 2. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] HEADS UP: PHP-5.5 Feature Freeze
Hi Internals, as you are aware we delayed the first beta by about 4 weeks to get Zend Optimizer in. This week will finally see the release of the first beta. This implies: No new features should be added to the PHP-5.5 branch from now on! RFC that are currently in voting phase can be merged once their vote finish. Everything else has to wait for 5.6. Fixing bugs, updating timezone db, etc in PHP-5.5 is obviously okay. Thanks, David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] HEADS UP: PHP-5.5 Feature Freeze
On 03/20/2013 01:51 AM, Stas Malyshev wrote: Hi! as you are aware we delayed the first beta by about 4 weeks to get Zend Optimizer in. This week will finally see the release of the first beta. This implies: No new features should be added to the PHP-5.5 branch from now on! RFC that are currently in voting phase can be merged once their vote finish. Everything else has to wait for 5.6. Fixing bugs, updating timezone db, etc in PHP-5.5 is obviously okay. What about https://wiki.php.net/rfc/array_column? It's in accepted but not merged. I could probably go over it over the weekend and try to fix remaining issues and merge it, is it ok for 5.5? I was looking into this today and there were some minor compiling errors. Rasmey is going to take care of them and I will merge it tomorrow before beta1. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution
On 2013-03-07, Rasmus Lerdorf ras...@lerdorf.com wrote: On 03/07/2013 09:01 AM, Anthony Ferrara wrote: So my proposal is to slow down for a minute and not call this RFC accepted or not until we can come to some consensus as to if it classifies as a language change or not... Better to clarify for the health of the project than to plow through and risk causing further strife... And how do you propose we do that? Vote on it? Will that vote need 2/3 as well? I think most of us accepted that language-level changes meant syntax changes. Things that add new features to the language itself. I think the only thing requiring a 2/3 vote would be the decision on wheather to enable it by default or not. As long as it's in ext/ and not enabled a 50% should be sufficient. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.5.0 Alpha 6 Released
Hi Internals, PHP 5.5.0 Alpha 6 has been released for testing. As you know we were supposed to release a first beta but due to the current voting on ZO+ we went for yet another alpha. This time, it's the last one. The packages can be found at: http://downloads.php.net/dsp and windows packages at http://windows.php.net/qa Please test the release carefully and report any bugs. We will begin with the beta stage in two weeks. March 19 will mark the last date for new features. During beta phase no new features will be allowed to get in. Therefore you have two weeks to get any feature additions, etc on. RFCs that are currently voted on and not finished before March 19 should not be included. Thanks for all the contributors. Regards Julien and David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution
On 03/07/2013 10:33 PM, Philip Olson wrote: I think the only thing requiring a 2/3 vote would be the decision on wheather to enable it by default or not. As long as it's in ext/ and not enabled a 50% should be sufficient. Shouldn't we be focusing on how this makes PHP better? And not nitpick about a percentage point or two? I agree, no need for lawyers and nitpicking. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP distribution
On 2013-02-27, Zeev Suraski z...@zend.com wrote: On 27 2013, at 18:58, Anthony Ferrara ircmax...@gmail.com wrote: Zeev et al, I just want to put my justification for the only if no delay vote. I voted that way because we're already at a significant delay. If this vote was a month ago when O+ was suggested first, I would definitely have voted for delay. In fact IIRC I proposed a delay back then. But after a month, I think delaying much further would be imprudent. Fair enough! Here's mine for delaying: I believe our users will much appreciate a release with an opcode cache that's several months delayed vs. one that's without an opcode cache several months early. If the 5.4 adoption rate (or complete lack thereof) is any indication - very few are eagerly waiting for 5.5. In fact, in a year's time, when we all gear up to release 5.6 (based on current frequency) - 5.5 is almost guaranteed to have next to no traction in our userbase. A bundled opcode cache might be the killer feature that makes the difference. I agree with zeev here. The opcode cache is one of the most important thing for adoption. With apc not being 5.4 compatible and 5.3 eol with 5.6, there is no real transition for people relying on an opcode cache if we don't delay 5.5. That's the only reason why Julien and I so far delayed it. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Give the Language a Rest motion (fwd)
On 2013-02-21, Rasmus Lerdorf ras...@lerdorf.com wrote: Personally I would love to see more RFCs focusing on performance and less on syntax changes. Of course, a syntax change RFC, and even the initial (often shaky) implementation of a syntax-related change is much much easier to whip up than the deep analysis, profiling and creativity required to find and come up with ways to make a complex piece of code faster or use less memory. +1. I think that the RFC process did the project very good and enabled new people and their patches into the project. Nevertheless we should be aware that a scripting language needs to be robust and fast. The more language syntax we add, the more complex the language gets and therefore it's quality as a very good beginners language. Also we just end up in the troubles we had over the last years when one could just hope that xdebug will catch up with new language changes (thanks to derick it usually does), and one knew that APC will not work. A lot of the language features in the last years didn't just make some people happy but also made others unhappy as they couldn't use the new language in production (and thats what counts). People are stuck with 5.3 atm because there is no opcode cache for 5.4 and the only good news for them is that the ZO+ RFC focuses and robustness and performance so the users will still have an opcache for a new version once 5.3 is EOL (in a year). (and i am not even talking about the headache everyone is already talking about because they used a lot of apc caching functions in their code and therefore are stuck with 5.3 for another 2 years and can just rely on distros for patching). So plesae when one talks about the userbase, make sure you just dont see you part of the bubble but all the others who are struggling with recent changes already. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Getting separate outputs with Date Functions
On 2013-02-19, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
echo date_create('@1361240634')-format('Y-m-d');
// output: 2013-02-19
echo date('Y-m-d',1361240634);
// output: 2013-02-18
timestamp dates are created with UTC TZ, date() assumes your configured TZ.
I ran into this myself and I personally consider date() assuming your
configured TZ A bug. Timestamps are defined as UTC and the behaviour of
DateTime is correct there, that it always assume UTC. date() should do
the same. But then date() behaviour has been that way since ages
and probably a lot of code out there is assuming the current TZ when
using date().
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 5.5 upcoming roadmap
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, so just to make this sure. We are NOT skipping the RFC. we are planning to merge it before beta1 IN CASE the RFC get's accepted. I believe a op cache is really important for the overall acceptance so I hope the RFC gets accepted. Nevertheless it's up to the author of the RFC to call for votes, but we as RMs just wanted to stretch the actual release dates as I think this RFC is important enough to justify such a step. David Am 15.02.13 19:08, schrieb Lars Strojny: Hi Julien, Am 15.02.2013 um 13:05 schrieb Julien Pauli jpa...@php.net: Hello everyone, As you may know, Zend recently open sourced ZendOptimizer+ with a PHP Licence. We are planning to merge it to PHP5.5 Core (discussions on Mailing lists and IRC) and have it bundled with PHP5.5 final release stable. I'm sorry, but you must be kidding doing such a change and skipping the RFC process altogether. This will seriously hurt the acceptance of the whole RFC process and there won’t be a good argument against people just committing random changes without an RFC. How should I convince somebody with a working pull request to go ahead and deal with an RFC when we introduce changes like that just like that. Can we please stop the process insanity and stick to our own rules (or change them in a transparent way). Thanks, Lars -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRHnsjAAoJEKSanlo0ToXKmXAP/AuKTYfcm3PZdrOu9nqDkg8x IjnsY5pMybDTbkJtLw96DT+5Zz24t9BdwBPwTRkKccLiYGavCQvV+ewdNUMEFrv7 kbuyi6tgRbB/aUpocKXbzq5CRk19YcIZr3E4HXpeMHcNhXGbFRmXvk8yMUWlTGMn Fsf6v9bs+4d/uCaSMr2jS56KgDTn9pseAbeDumj3L+EAZYF+k/lz0YuxNC7X3EUv HclKiPBLroaYz0q4Yg+BHuBsCgkhGnzwxNlYfkCPHh8mZZFxUtcIkONgILgxsGMA +ik51JzspZRkdvr+TpvE6Va5O52i3C31wxKelr4f2+dgDO7v28tqOxrOHYVZgpdY NK3GOYDgp1YgphY0CY/J0IrK2yLjdqois7qynuyAwP7DxE/ytz6HFs4UuzPdM6Ry sFXua/L5JFzHHO4jU1x47BDM/Blre2COQaMdB1GE2hgFIjKqU5cQRHxMG6VzGCct UiWik8/1sLQKoMFQnSMBHbidlYbDCKd4kW2dyKjKw9Ok3MfW08VPZ/SBJNB2RDYP aYD4OcVe9SE9kuJEP0sxs9f/s4xMmkiP6AYa/2e2L4UqfoT0bo20HrrA50h0lKXb hkj/yOWB9f6qy3qUhDK5EdbSPK5i18cS5jWcseXLjHlE/xADWGrTyjAg2flaKAQT xF5/opO8pfoi4PY6osQT =iZJN -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Voting periods
On 2013-01-28, Zeev Suraski z...@zend.com wrote: --e89a8fb1fbd85c066a04d455d2d7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The specific case in point is https://wiki.php.net/rfc/propertygetsetsyntax-v1.2 - which while has more supporters than opposers, consistent fell short of the 2/3 majority it needs to be approved. The vote should have ended on Wednesday =E2=80=93 4 = days ago, but for some reason it=E2=80=99s still open. It=E2=80=99s time to clo= se it. I agree. We need a defined period for voting. The past RFCs have seen very short voting periods to very long, depending on what the RFC creator wanted and usually worked in his favor. To make it more objectiv and actually concentrate on code instead of votings I tihnk a 1 week or 2 week period after calling for votes is okay and shouldn't be able to be extended. Concerning the property syntax, I agree that this vote should be closed already. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [RFC] Integrating Zend Optimizer+ into the PHP distribution
On 2013-01-29, Zeev Suraski z...@zend.com wrote: --e89a8fb1f5b0f501b204d468d53f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable All, Following the discussion at the end of last week, I prepared a draft RFC for the inclusion of Optimizer+ in PHP. In parallel we=E2=80=99re in the process of prepping the source code for independent public consumption, which I hope we can be done with by the end of next week, hopefully sooner. https://wiki.php.net/rfc/optimizerplus Comments welcome! As already said in this thread, the major issue for 5.4 adaption was APC, so I really like that we get a 5.5 compatible optimizer. We are planning to go into beta mode next week which is a feature freeze. Therefore optimizer would not make it in, but I think as the code is already mature and not just a random new feature I think we can allow this into core during beta phase, maybe for 5.5 disabled by default. Anyhow we are already late with 5.5.0 and I dont want a 5.5.0 release in May. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] HEADS UP: Upcoming Feature Freeze for PHP 5.5.0
Hi Internals, as you might have read in the 5.5.0alpha4 announcments, we are moving forward with 5.5.0. We are already a bit late on the schedule and we want to begin the beta cycle in 14 days and concentrate on QA for the 5.5.0 release from now on. This includes a feature freeze. No new features should be comitted to the repository once we tagged the first beta on Feb 7. All outstanding features will have to wait for 5.6.0 in a year unless there is a really good reason for an exception. Feature Freeze is on Feb 7, 2013. Regards, Julien and David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: com php-src: fix bug #63462 (Magic methods called twice for unset protected properties): NEWS Zend/tests/bug63462.phpt Zend/zend_object_handlers.c
On 2013-01-18, Stanislav Malyshev s...@php.net wrote: Commit:33b104c778c5c0e5446671397aaddd66efa4a7bc Author:Stanislav Malyshev s...@php.net Mon, 14 Jan 2013 00:06:09 -0800 Parents: f63a9f6c11c05aa76158b6cae0e05340d303a6af Branches: PHP-5.3 PHP-5.4 PHP-5.5 master Link: http://git.php.net/?p=php-src.git;a=commitdiff;h=33b104c778c5c0e5446671397aaddd66efa4a7bc Log: fix bug #63462 (Magic methods called twice for unset protected properties) this appears to break tests/classes/unset_properties.phpt on 5.5 branch, can you please look into this? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: com php-src: Fixed bug #64007 (There is an ability to create instance of Generator by hand).: NEWS ext/reflection/php_reflection.c ext/reflection/tests/bug64007.phpt
On 2013-01-19, Xinchen Hui larue...@php.net wrote: Commit:f7b99c481d0a943d922e99ad9afa82c45193030e Author:Xinchen Hui larue...@php.net Sat, 19 Jan 2013 17:01:57 +0800 Parents: e23fca8910b96f1c3bb26c6582c17c92fd6f2f7a Branches: PHP-5.5 Link: http://git.php.net/?p=php-src.git;a=commitdiff;h=f7b99c481d0a943d922e99ad9afa82c45193030e Log: Fixed bug #64007 (There is an ability to create instance of Generator by hand). Use get_constrctor instead of access of the ce-constructor directly please note that this breaks ext/pdo/tests/pdo_036.phpt on the 5.5 branch. Please take a look! -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] [RFC] Reflection annotations reader
On 2013-01-09, Rasmus Lerdorf ras...@lerdorf.com wrote: On 01/09/2013 04:16 AM, Derick Rethans wrote: On Tue, 8 Jan 2013, Rafael Dohms wrote: 1. The syntax is crap: this is solvable, let's find the right syntax Any extra syntax makes the PHP parser more complicated (and arguably slower). I don't want to have it slower/more complex for some arbitrary extra syntax just for some weird annotations. This is my worry as well. Especially when it comes to opcode cache support. Most of the patches I see these days completely ignore the opcode cache side of things which needs to change. For any large language-level change, any implementation that doesn't also include an APC diff, or at least a very complete explanation of how it will be generally supported by opcode caches just isn't complete. I totally agree. So far people are asking me if apc is 5.4 compatible as they want to move to 5.4. Lacking support for APC is a real problem for people to adopt recent versions and with even faster release cycles we should keep think more about APC when we introduce new features. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.5 Release Schedule
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Internals, I think with the start of recent 5.3 EOL discussion, it's about time to give an overview over the 5.5 schedule as far as I planned it. I want to go for a new alpha this week (on thursday), 4 week after the first one. I should have send out a mail two days ago but missed it. Sorry for that, I'll do a better job with alpha3. - From there I want to go with a new alpha in about two weeks, as we there are some things like ext/mysql deprecation in the pipeline. After alpha3 we have to check if there is something urgent in the pipe to do a alpha4. If not I want to go into beta phase for 2 betas. The beta phase also marks the feature freeze, so no new features should be added from there on (e.g. mysql deprecation should be done in alpha phase). I hope that after 2-3 betas we can go to a first RC. During 5.4 we needed a lot of RCs, so I assume a 5.5.0 final can be expected around April. I know this schedule is tight and some might not agree, but it's the first release in the new 1 year timeframe so we have less features then 5.4 and 5.3 to release and will release php-next in about a year from know, so we are not in a hurry to just push everything in if it's not ready. I am confident that the current open alpha window is good enough for whats about to get merged and that 8-12 weeks of betas and RCs are enough to stablize for a final version. The schedule for the next 6 weeks is as follows: 15. Nov 2012 (past) - 5.5.0 alpha1 13. Dec 2012- 5.5.0 alpha2 27. Dec 2012- 5.5.0 alpha3 14. Jan 2013- 5.5.0 beta1/alpha4 (feature freeze) Julien and I will update http://wiki.php.net/todo/php55 over then next days with what's left to do. - - Julien and David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQx5pCAAoJEKSanlo0ToXK6tkP/R32cQxYOPWW+NsaxVWfTkBi lAkolOXdacdLa7sZR8dNSdZQ8llhoGq1KyWnD9eLYchiilBF/NS3mz6hIdKnd9un TaSD+1i9bN487+Or5Q1fYAQyXLR7BfYznpcOE2bVDK9+hpM2unNfcyGjeg05cjBp dC3LmO++KrU6TvGSSw1+GoQnoKmtB37/HOib7a4jGyOes4PJjw7hW/J1QSJ/lKTm UxksKweJ8GC8EiAJGNw/OUzyBH2h0Tdtzu3Jd5NdRkDwqVXeacBE9dhyx8M1NKPf hbXwZHd+2zKHRXbUftUyQTSYAhFbEZNvqxyW4AgOefyBIz322frJGiLN9eXAEYt5 evrj1T40SExMiipxQMTo9qqc9XsfGoFYz6RbCZS4MVLmiaxawO9coh3p1/C/PCi9 bDi/G/EBuALa8kiklNMbxnuIbRClDbNWBFYvlx90oJWFAztPl38dqoAMxoLdAftx smIeFLNL5PxNuXEbUZEekqxgAfo+BWqzUu7ToQNDI4XrRuw2g2VAMRGWflcBjkc1 /Rfkq7yP3ccIyAtGQ6x/YuzNGK9uyyxCYpeuGj2XXahpz8QDE4byBR9S8PC0wqqy Fr2pWlZf2gXj9KtrAzp4eP3fvj1kZ5LgzBgOAo2roBJM4zkA51EhBy2B3JuM+0Gn AggTRjwqTkytNSS/hhMc =HCsP -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Git Access
On 2012-12-05, Sara Golemon poll...@php.net wrote: remote: Welcome pollita. remote: Changesets accepted. Thank you for your contribution. remote: remote: Attempting to push to mirror g...@github.com:php/php-src.git remote: Write failed: Broken pipe remote: fatal: The remote end hung up unexpectedly To https://git.php.net/push/php-src.git c058ed5..5ac3577 master - master The push to git.php.net succeeded, but its push to github failed. Is there a process that deals with keeping the repos in sync in events like this? No, the next push will sync it again. I can setup a cronjob to do that every 15mins. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Cannot build PHP-5.5 with --enable-dtrace on Fedora 17
On 2012-12-06, Sebastian Bergmann sebast...@php.net wrote: I brought this up on #php.pecl yesterday and David already investigated a bit but I thought I should probably bring this up here as well. I cannot build PHP-5.5 with --enable-dtrace on Fedora 17, details are here: https://gist.github.com/4214282 Yes thanks for creating a ticket. Assign it to me. I'll look into it, sadly though I cannot reproduce it yet, even though I run Fedora 17 (fedora, yay!) as well. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: PHP 5.5.0alpha1 Released for Testing!
On 2012-11-15, d...@php.net d...@php.net wrote: Hi Internals, as announced a few weeks ago, we tagged PHP 5.5.0alpha1 on Tuesday. This release marks the start of 5.5.0 release process. The packages can be found at: http://downloads.php.net/dsp Windows builds are up at http://windows.php.net/qa/ Regards David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] HEADS UP: PHP-5.5 branched.
Hi Internals, with the first alpha going to be tagged today and officially released on Thursday, I went ahead and created the 5.5 branch. Merging should be still straight forward, but it's going to be 5.3 - 5.4 - 5.5 - master. I know this is a mess, but I think we'll have to live with that for a while. Therefore bigger BC breaks can be applied to master as well. Following the versioning scheme of 5.4.x version, I versioned master as 5.5.99 until we decide if it's going to be a 5.6.0 or a 6.0.0. Again, if someone wnats to come up with a better plan to have a branch open for bigger BC breaks and creating less branches, let us know. For reference: PHP-5.5 is still open for new features. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] HEADS UP: PHP-5.5 branched.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Makes sense, I'll bumped the version to 5.6.0-dev On Tue 13 Nov 2012 08:23:31 PM CET, Derick Rethans wrote: On Tue, 13 Nov 2012, Johannes Schlüter wrote: On Nov 13, 2012, at 18:44, David Soria Parra d...@php.net wrote: Following the versioning scheme of 5.4.x version, I versioned master as 5.5.99 until we decide if it's going to be a 5.6.0 or a 6.0.0 Repeating what was said for 5.4.99: I don't think this is good. This makes version comparison harder. Use 5.6.0-dev. We can increase to 6.0 or 10.0 as needed. +1, and also bump PHP_VERSION_ID to 50600 for that one please! cheers, Derick -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQoqLhAAoJEKSanlo0ToXKAgEP/iGi/oPhO4GpcjYSSu+Dactj CE4eA4jJdT2J8cGJo8iULgrXgRAS83nFYfIXgPNOTOwbdrd467YxJjpLGtToJWsO oYofZs667MVZepaU0RhIXIYJgchWgrd17Su41Gkc+trff+LeaCfBHFlKTsb0w4vt s0SMDuryRnTBSJzjcdiURP3kB+oBXHVo/kSt4oTBpTcEsLVLThXGtTCtNa1A5VSV 4oJw0K7y5QboTj8oqKpZdIocYkyI08ybGeRCG2BK7hIVCFcQmdAlZntPCNbYn27W j+MEGg8XzZxCnld964rOo4IKcBPsATyrK8JeQI9QNf5eYUR/AD+uYDJpce+OQ/+2 mJ53AYNnexL+IXvl/8lFR21nbzS/OQKE7+yrui4lzXIJrm1/gKygqgVyOttwds/S gVMDM17/8uC7oVqtOT38enue79EGNmRsfvAydTm4+cVx3Y9RyAnIqhbc9Aq6zHif dkzxv4aDowoaVwh9QidiuFZDiGal1nRozrAVdQD4nZwTHgpo5bq1u5oX4uZi/N16 Gduy8hwBqKiVbbmpUUj++rm25LqpAK+AYYWW7Am5cbRegEwOT2D+1vEAxTJl5rkb bysJ8pc1NwiPFdhaPVhV2mq5uNyEqyTNvj2nVJCJFV6As3g2K29phzPKuTyKNq9D NA41oe0MAA7LvsKCigh7 =KuW9 -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] RFC: ext/mysql deprecation
On 2012-11-13, Adam Harvey ahar...@php.net wrote: On 13 November 2012 01:16, Ferenc Kovacs tyr...@gmail.com wrote: On Mon, Nov 12, 2012 at 4:00 PM, Ulf Wendel ulf.wen...@oracle.com wrote: Don't bother. There is a standard way of deprecation, at least I assume there is. Its proven. Use it: docs warnings, E_DEPRECATED, remove. I agree to deprecate/remove on the long run, but I think that we should wait for the next version for doing so. Honestly, if we were going to delay the eventual removal (and I'm not sure we should), I'd rather have an extra release cycle with E_DEPRECATED, rather than an extra release cycle with documentation-only warnings that are more easily ignored ? so either way, I'd still want the notices in 5.5. Personally I think we should E_DEPRECATE it. We will have enough time till 5.5 RC1 to decide on the RFC within the regular 2-4 weeks. +1 from me. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] PHP 5.4.9RC1 next Tuesday
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, yes, I clearly slid when I was looking at the calendar. It's Tuesday 13th. David On Mon 05 Nov 2012 02:18:59 PM CET, Renan Gonçalves wrote: A logical thought leads me to Tuesday 13th, November 2012. On Sat, Nov 3, 2012 at 7:45 PM, Sherif Ramadan theanomaly...@gmail.comwrote: On Fri, Nov 2, 2012 at 11:21 AM, David Soria Parra d...@php.net wrote: Hi Internals, I was asked to send heads up before pushing an RC, so here we go: As we were a bit busy this week we had to postpone the RC to next Tuesday. So 5.4.9RC1 will be tagged on Tuesday and released on Thursday. 5.4.9 final will be tagged on 2012-11-19 and released on the 22th. As I am focusing on 5.5, Stas is doing 5.4 on his own now. I am still doing releases for 5.4 in case Stas is busy or otherwise not available. And don't forget, 5.5.0 alpha1 is going to happen on Thursday 15th and tagged on Tuesday 12th. Tuesday 12th? The 12th of what? There is no Tuesday the 12th in the coming months. - David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQl8RVAAoJEKSanlo0ToXKWUkP/0/4ZPxnxt0HXK07zh5iiOzz HNHUrWlgz1wxZVxZN8ZnPC9Ywp7vQ4WUSCtz+TqpNgLBeivQ1u9p989GKWzxRK8k 4YASEFMltP2UfZDjxbUCq82JU8+5TRTRDOetm8Ue1hyyI9gqq3B1MST+d9pnykbs F1srnrW2jbaurHgTPj132PoUyjXCaIx0TT0ns2xULz31Jka//fQrXBm7Q0PDFevk bBKN2RsANzF5PFlSYEOZzpP+A20+oUNsXFqhG8I66c5j6nY+5XOnbykXBLk1+8kR u1uv7rT+jB9P0Gd9hvtH+cvJBijQXTUB69mPrnmo6xt3WXhMsjpjyOx/PbrvH3b+ cXhVCoW2EI5PmnC41TgGei2knR6X3xmx0cQk5iAH9trB4RJSGzEb59YN0CIfQlMX 5c7rAOFEzSRgqYnsBb3J1HZMwjx81aDKAV1R7acBmZeax7hfUauSjvTD1g4YPvxl SmpDiGUTHmdKc4N2XlKc19I/b1SiYhSBRkz2C8RWPLVHOm7AyFz/JhRnJRmSy73N MQvWdCKDbsoDIM4VJY7FFYWa/nYyJhxbIDQqCEd5csewYBAUxNn8os2Mb6QKJqpA EW9WdxrqZC4DTHtgDlFXCyfGnrGZSpZhiD/5Wn2He8gdaw/qz0SYGiuJBKum7Pc3 yakXGYHKajtzetHVmxn9 =2ocL -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.4.9RC1 next Tuesday
Hi Internals, I was asked to send heads up before pushing an RC, so here we go: As we were a bit busy this week we had to postpone the RC to next Tuesday. So 5.4.9RC1 will be tagged on Tuesday and released on Thursday. 5.4.9 final will be tagged on 2012-11-19 and released on the 22th. As I am focusing on 5.5, Stas is doing 5.4 on his own now. I am still doing releases for 5.4 in case Stas is busy or otherwise not available. And don't forget, 5.5.0 alpha1 is going to happen on Thursday 15th and tagged on Tuesday 12th. - David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Moving forward: PHP 5.5
On 2012-09-08, David Soria Parra d...@php.net wrote: Hi internals, I would like to go ahead and propose Julien Pauli as the RM for 5.5. He is an active member of the PHP.net community, has deep knowledge of the internals and the necessary backing from his company to be able to dedicate the time needed to do the job. Knowing that things are kindof rough at the start, I am willing to help out with intial releases, reviews and settings things up until they can be handled by one person (which is pretty much the state of 5.4 atm). A last bump on that. So nobody complained so far, I think Julien and I can go ahead and start with 5.5 as soon as possible. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Moving forward: PHP 5.5
On 2012-09-17, Sebastian Bergmann sebast...@php.net wrote: Am 17.09.2012 17:36, schrieb Johannes Schl?ter: There are very few special processes. In fact the only RM-specific things are around packaging the tarballs up, while that's described in an README. Does this have to be manual process? Is there something in it that cannot be described in a Makefile, build.xml, etc. instead? Yes, merging NEWS, writing news entries, mails and generating Changelog-5 (the issue is related to NEWS). Most of the rest can be automated so once a release hit .0 it's, as johannes pointed out, very straight forward -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Moving forward: PHP 5.5
Hi internals, it's been a great eight months now for PHP 5.4. We released 5.4.0 final in february and since then we were able to deliver a new PHP version every month (thanks to the hard work from stas). As most people know we do not include patches in 5.4 that will break backwards compatibility. Those patches are in the 5.5 branch and we are also stockpiling some new features. We have implementations for foreachlist, generators, hash_pbkdf2 and others are likely to get included in the next weeks like the simplified password hashing API. Following the release process RFC, I would like to start discussing the beginning of the 5.5. series, that can include new features, do bc breaks if necessary and overall provide a smooth move to a new series without having the branches diverge for years and years again (like 5.4 and 5.3). Last but not least, 5.3 is out since 2009 and it would be good to put the series into a security fix only mode and give it an eol. So I proposed to start off with 5.5 and focus on it, so we can get a release going till Feb/March 2013. As with every new release minor release (read minor as the Y in 5.Y.Z), we choose a new RM. We had quite some confusion and debates around this topic the last time, so I'll just go ahead and propose somebody right away for the job. I would like to go ahead and propose Julien Pauli as the RM for 5.5. He is an active member of the PHP.net community, has deep knowledge of the internals and the necessary backing from his company to be able to dedicate the time needed to do the job. Knowing that things are kindof rough at the start, I am willing to help out with intial releases, reviews and settings things up until they can be handled by one person (which is pretty much the state of 5.4 atm). If you can think of a better candidate or want to step up, feel free to do so. Let's keep things simple here, stay on topic and debate if we want to start with 5.5 and who can RM it. - David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.4.7RC1 released for testing
Hi! We've released PHP 5.4.7RC1 which can be found here: http://downloads.php.net/stas/ Windows binaries as always are at: http://windows.php.net/qa/ This is a regular bugfix release, the full list of issues fixed can be found in the NEWS files. Please test and report if anything is broken. If no critical issues is found in this RC, the final version will be released in two weeks. Regards, Stas Malyshev and David Soria Parra -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.4.6 and PHP 5.3.16 released!
Hello! The PHP Development Team announces the immediate availability of PHP 5.4.6 and PHP 5.3.16. The releases fixes over 20 bugs. All users are adviced to update to PHP 5.4.6! Alternatively, PHP 5.3.16 is recommended for those wishing to remain on the 5.3 series. PHP 5.4.6: Release Announcement: http://www.php.net/releases/5_4_6.php Downloads:http://php.net/downloads.php#v5.4.6 ChangeLog:http://www.php.net/ChangeLog-5.php#5.4.6 PHP 5.3.16: Release Announcement: http://www.php.net/releases/5_3_16.php Downloads:http://php.net/downloads.php#v5.3.16 ChangeLog:http://www.php.net/ChangeLog-5.php#5.3.16 regards, Johannes, Stas and David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.4.5 and PHP 5.3.15 Released!
Hello! The PHP Development Team announces the immediate availability of PHP 5.4.5 and PHP 5.3.15. The releases fixes a security issue in the stream implementation and over 30 bugs. All users are adviced to update to PHP 5.3.15 or PHP 5.4.5! PHP 5.4.5: Release Announcement: http://www.php.net/releases/5_4_5.php Downloads:http://php.net/downloads.php#v5.4.5 ChangeLog:http://www.php.net/ChangeLog-5.php#5.4.5 PHP 5.3.15: Release Announcement: http://www.php.net/releases/5_3_15.php Downloads:http://php.net/downloads.php#v5.3.15 ChangeLog:http://www.php.net/ChangeLog-5.php#5.3.15 regards, Johannes, Stas and David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.3.14 and PHP 5.4.4 released!
Hello! The PHP Development Team announces the immediate availability of PHP 5.4.4 and PHP 5.3.14. The releases two security related issues and over 30 bugs. The release fixes two security issues: A weakness in the DES implementation of crypt() and a heap overflow issue in the phar extension. All users are adviced to update to PHP 5.3.14 or PHP 5.4.4! PHP 5.4.4: Release Announcement: http://www.php.net/releases/5_4_4.php Downloads:http://php.net/downloads.php#v5.4.4 ChangeLog:http://www.php.net/ChangeLog-5.php#5.4.4 PHP 5.3.14: Release Announcement: http://www.php.net/releases/5_3_14.php Downloads:http://php.net/downloads.php#v5.3.14 ChangeLog:http://www.php.net/ChangeLog-5.php#5.3.14 regards, Johannes, Stas and David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Git misses to archive old Zend code
On 2012-06-03, Yasuo Ohgaki yohg...@gmail.com wrote: Hi, I noticed that old PHP source in git lacks Zend directory. Perhaps, all Zend Engine 1? php-4.4.9 tag http://git.php.net/?p=php-src.git;a=tree;h=43c2df47e3782bcc0975f165b77fde40daa96b14;hb=a4d3a4d2ca89c80f37dca11a4e0eee1ef187ba18 php-4.3.11 tag http://git.php.net/?p=php-src.git;a=tree;h=c4501016befc8bb37e12300b9c1e0472555a84ab;hb=969b51472110145554ee84c663cacf02344d8173 They are missing in SVN as well http://svn.php.net/viewvc/php/php-src/tags/php_4_4_9/ E.g. the php-4.0.5 tag is complete As we imported everything from SVN the Zend directories are missing in the tags you named as well -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] boolval() again
Going through the 26 open pull requests (please let us work on getting that number down), I stumbled over https://github.com/php/php-src/pull/60. This was already proposed on the mailinglits, but the thread died fast without a satisfying answer on whether to add a function boolval() or not. Personally I would like to see the function in. Having a complete set of XYZval() functions is a good reason for me to add that function. The implementation is simple and straight forward and easy to maintain. Do we need an RFC for that simple pull request or can we just go ahead and pull it? David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Git misses to archive old Zend code
On 2012-06-03, Yasuo Ohgaki yohg...@gmail.com wrote: Hi, I noticed that old PHP source in git lacks Zend directory. Perhaps, all Zend Engine 1? Thanks i'll take a look -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.4.4RC2 Released
Hi! We would like to announce the second RC of the 5.4.4 version. This is mainly a bugfix release. The release includes a fix for a weakness crypts() DES implementation (CVE-2012-2143). Please test it and notify us of any problems you may encounter. The full list of the fixes is as always in the NEWS file. You can download the packages from: http://downloads.php.net/stas The Windows team provides windows binaries for the release. As always you find them at: http://windows.php.net/qa/ We plan the next RC for 5.4.4 in two weeks. Regards, Stas David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.4.3 and PHP 5.3.13 Released!
Hello! The PHP Development Team announces the immediate availability of PHP 5.4.3 and PHP 5.3.13. The releases fix security related issues in a previous attempt to fix a CGI vulnerability (CVE-2012-2311). PHP 5.4.3 also contains a fix for a buffer overflow vulnernability in apache_request_headers (CVE-2012-2329). The PHP 5.3 series is not affected. All users are adviced to update to PHP 5.3.13 or PHP 5.4.3! PHP 5.4.3: Release Announcement: http://www.php.net/releases/5_4_3.php Downloads:http://php.net/downloads.php#v5.4.3 ChangeLog:http://www.php.net/ChangeLog-5.php#5.4.3 PHP 5.3.13: Release Announcement: http://www.php.net/releases/5_3_13.php Downloads:http://php.net/downloads.php#v5.3.13 ChangeLog:http://www.php.net/ChangeLog-5.php#5.3.13 regards, Johannes, Stas and David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.4.1 and PHP 5.3.11 Released!
Hello! The PHP Development Team announces the immediate availability of PHP 5.4.1 and PHP 5.3.11. The releases fix security related issues in the name validation of uploaded files and the handling of open_basedir in the readline extension. Support for Apache 2.4 was added and over 60 bugs were fixed. Users are strongly encouraged to upgrade. PHP 5.4.1: Release Announcement: http://www.php.net/releases/5_4_1.php Downloads:http://php.net/downloads.php#v5.4.1 ChangeLog:http://www.php.net/ChangeLog-5.php#5.4.1 PHP 5.3.11: Release Announcement: http://www.php.net/releases/5_3_11.php Downloads:http://php.net/downloads.php#v5.3.11 ChangeLog:http://www.php.net/ChangeLog-5.php#5.3.11 regards, Johannes, Stas and David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Some Stats
On 2012-04-17, Rasmus Lerdorf ras...@lerdorf.com wrote: Number of posts to the commit list since Jan.1,2012 (top 25): Number of commits to php-src (excluding merges) since Jan.1,2012 (top 15): 126 Xinchen Hui 83 Rasmus Lerdorf 79 Gustavo Andre dos Santos Lopes 73 Pierre Joye 62 Anatoliy Belsky 53 Stanislav Malyshev 46 Dmitry Stogov 45 Christopher Jones 36 Johannes Schlueter 32 Michael Wallner 29 Ilia Alshanetsky 28 Nikita Popov 17 Nuno Lopes 15 Derick Rethans 14 David Soria Parra -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Release day, was: release process with git
On 2012-04-17, Stas Malyshev smalys...@sugarcrm.com wrote: Hi! The whole point of releasing on Thursdays is so sysadmins have the chance to update their servers in the event of known security problems before the weekend. This point however becomes void when we release late Thursdays evening American time, and we could just as well release on Saturday nights as noone in Europe will be able to update their servers, and the Americans will probably not be updating theirs either when they notice the release Fridays after lunch. I tag and package Wednesday evening US Pacific time. I can change the Wednesday part, but not the evening US Pacific part, at least not until I move to a different timezone. If current schedule is not satisfactory, I have nothing against moving it to Tuesday. Pretty much any day is OK with me, so let's see what people think. Yes at the moment we have the problem that: Stas tags Wednesday evening US Pacific time Stefan builds Thursday during the day US Pacific time David announces after all this is done which is Thursday evening EU time sometimes it becomes so late that I can only do it friday morning. So if we want to release Thursday, then windows builds need to be done one Wednesday. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: solving most git issues and questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please add all your questions here: https://wiki.php.net/vcs/gitfaq-usecases And let try to answer them one by one, for the best or recommended way to do something. Thank you. makes sense to put it into the wiki and discuss it :). First of all I added some solutions. We can comment on those and find the recommended way to do it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPiCLHAAoJEAT0aMuPE7Z1hR4P/i69+bEvGBPntR3iU7ma/OZe IRYz062XXyzZ3VlGoY36S4q9gJwimytXxRH2cs9ClLKlYh4N739QPNRJ3tfPkVZW eKz4A/lg4aN45KInRQoyV2XnGB3wjXcBVrGrsfl5MZr53Fz3yxb/OjKupbgiVCWs TgxJODzhoHiivxxxWF2RFl8MSsyQvDDxGdgDpeKMcy97HCUOhKYT2jmSt4PR6Qdc atVFF/mh5kB7qdHAkon4yRr5ypy/+HvkaTR2xIvR+ukK7mXVyUt92ceOg2fWACJm vqXhu2iJHizeVe2hdHCOrlVmuliUtHUlxcR8eAhqBD2Td0rzEbuIbd4oRb8QZnq5 UluKxu9iw9AzujIIhhpHrIlNVUjuYROezmLDEzBn2LDnavoNWqQi328hKqmA39+4 n+DS5U+QXw6Qf1aupCIypNgkYDfx8J5+Zp9hoQgVB43d7E6OuEzV3cmTESRITGeN xYbHNhRybuxERqXSn8InWpm9FdNhBAT6VL3xwdun2h1hHgC70UpR9DohoatxsJE6 HX9r02yn18mua9G6uGM2BpVs1nUilRslkEXjdGiy2rgYfD0nLkOBE/QmpFH4nVO+ o5kaKnUHkntFPF1SiIZVlMLR4y4l+rzrYtrGRZJGx79lKUrlKcIECg5yswn8Y+/4 5rz9PJiq7JgAqu91SPBs =Z/7r -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Question about parser implementation details
On 2012-04-01, Florian Anderiasch m...@anderiasch.de wrote: Hey there, due to the widespread acceptance of binary number format (0b1010101) and the growing demand for backwards compatibility I've started to work on support for Roman Numerals (I, II, III, ...) As you might know, this format cannot be strictly parsed from left to right or right to left, as several number values need a look-ahead before being able to compute them (like IV), so my naive first implementation splits the string into tokens (like in 1990 = MCMXC = M,CM,XC = 1000,900,90) then simplifying those 3 on their own, then adding the results, but I'm not sure this could kill performance if calculated inside zend_language_scanner.l. Thanks for the work on it. I really appreciated and would love to see roman numberes finally get implemented. I think a fair asusmption is that there is a certain ordering. First add numbers unless you encouter a higher or lower number: (1) in case current number == previous number, add it to your temp buffer (2) in case current number previous number, add it to your temp buffer (3) in case current number previous number, substract it from temp buffer Obviously you need to check if hte number is valid too: IIVM is obviously wrong But i think this is a good start. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: com php-src: Merge branch 'PHP-5.3' into PHP-5.4: main/SAPI.h
On 2012-03-31, David Soria Parra d...@php.net wrote: Commit:3bf53aa911e1e2128a11aee45c126000635de006 Author:David Soria Parra d...@php.net Sat, 31 Mar 2012 09:34:25 +0200 Parents: aa774a51d5c45b98103e0f67914d4c0b152e80ae ff8be9845f14a8156e7551033c2e98dad459f6fd Branches: PHP-5.4 master Link: http://git.php.net/?p=php-src.git;a=commitdiff;h=3bf53aa911e1e2128a11aee45c126000635de006 Log: Merge branch 'PHP-5.3' into PHP-5.4 * PHP-5.3: Cleanup Safe Mode related comment in SG(request_info) Changed paths: MM main/SAPI.h The diff is strange. Git and Gitweb show both that just the comment changed. The diff here displays the overall differneces between SAPI.h in PHP-5.3 and PHP-5.4 and not what I actually changed. I verified that the SAPI.h on the PHP-5.4 branch just had the comment removed. Diff: 3bf53aa911e1e2128a11aee45c126000635de006 diff --combined main/SAPI.h index f868f85,9a063d3..8f2536b --- a/main/SAPI.h +++ b/main/SAPI.h @@@ -105,7 -105,6 +105,6 @@@ typedef struct /* this is necessary for the CGI SAPI module */ char *argv0; - /* this is necessary for Safe Mode */ char *current_user; int current_user_length; @@@ -129,11 -128,8 +128,11 @@@ typedef struct _sapi_globals_struct long post_max_size; int options; zend_bool sapi_started; -time_t global_request_time; +double global_request_time; HashTable known_post_content_types; +zval *callback_func; +zend_fcall_info_cache fci_cache; +zend_bool callback_run; } sapi_globals_struct; @@@ -193,9 -189,9 +192,9 @@@ SAPI_API void sapi_handle_post(void *ar SAPI_API int sapi_register_post_entries(sapi_post_entry *post_entry TSRMLS_DC); SAPI_API int sapi_register_post_entry(sapi_post_entry *post_entry TSRMLS_DC); SAPI_API void sapi_unregister_post_entry(sapi_post_entry *post_entry TSRMLS_DC); -SAPI_API int sapi_register_default_post_reader(void (*default_post_reader)(TSRMLS_D)); -SAPI_API int sapi_register_treat_data(void (*treat_data)(int arg, char *str, zval *destArray TSRMLS_DC)); -SAPI_API int sapi_register_input_filter(unsigned int (*input_filter)(int arg, char *var, char **val, unsigned int val_len, unsigned int *new_val_len TSRMLS_DC), unsigned int (*input_filter_init)(TSRMLS_D)); +SAPI_API int sapi_register_default_post_reader(void (*default_post_reader)(TSRMLS_D) TSRMLS_DC); +SAPI_API int sapi_register_treat_data(void (*treat_data)(int arg, char *str, zval *destArray TSRMLS_DC) TSRMLS_DC); +SAPI_API int sapi_register_input_filter(unsigned int (*input_filter)(int arg, char *var, char **val, unsigned int val_len, unsigned int *new_val_len TSRMLS_DC), unsigned int (*input_filter_init)(TSRMLS_D) TSRMLS_DC); SAPI_API int sapi_flush(TSRMLS_D); SAPI_API struct stat *sapi_get_stat(TSRMLS_D); @@@ -211,7 -207,7 +210,7 @@@ SAPI_API int sapi_force_http_10(TSRMLS_ SAPI_API int sapi_get_target_uid(uid_t * TSRMLS_DC); SAPI_API int sapi_get_target_gid(gid_t * TSRMLS_DC); -SAPI_API time_t sapi_get_request_time(TSRMLS_D); +SAPI_API double sapi_get_request_time(TSRMLS_D); SAPI_API void sapi_terminate_process(TSRMLS_D); END_EXTERN_C() @@@ -240,8 -236,8 +239,8 @@@ struct _sapi_module_struct char *(*read_cookies)(TSRMLS_D); void (*register_server_variables)(zval *track_vars_array TSRMLS_DC); -void (*log_message)(char *message); -time_t (*get_request_time)(TSRMLS_D); +void (*log_message)(char *message TSRMLS_DC); +double (*get_request_time)(TSRMLS_D); void (*terminate_process)(TSRMLS_D); char *php_ini_path_override; @@@ -254,7 -250,6 +253,7 @@@ char *executable_location; int php_ini_ignore; +int php_ini_ignore_cwd; /* don't look for php.ini in the current directory */ int (*get_fd)(int *fd TSRMLS_DC); -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Confusing Windows Users 101...the download page is UNUSABLE.
On 2012-03-31, Thomas Hruska thru...@cubiclesoft.com wrote: I've been writing software for Windows in Visual Studio since forever and also know user-land PHP like the back of my hand and, even after a few Google searches, I'm still scratching my head over which PHP Windows binary download I want to use. If *I* can't figure out which version is appropriate, neither can the average web developer. Fixing the Windows binary download page so that it is USABLE by the average user should be priority #1. Thank you for letting us know about the potential problems of the windows download site. Feedback is alwahys appreciated. Why not go ahead and help out? Feel free to fork the windows website on https://github.com/php/web-windows and open a pull request. Thanks -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Pre-receive-hook doesn't accept a empty diff commit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 alex fixed that Am 30.03.12 15:08, schrieb Laruence: Hi: Today I make a fix which is only affect 5.3's test . after fix, I pushed it. then I do a fake merge(merge -s ours) in 5.4, then when I try to push it.. I got an error: remote: We cannot figure out what you comitted! To g...@git.php.net:php-src.git ! [remote rejected] PHP-5.4 - PHP-5.4 (pre-receive hook declined) then I have to make a trivial change to avoid this.. is this a bug? or what should I do in such case? :) thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPdfcoAAoJEAT0aMuPE7Z1aokP/i8/q5860XgBFJRLQfx3QQT6 Z5WbQGbnixllQrSKV6ywPZ8/ccM2j0KmT3Ei3d3jycfb8CMcwcJIiTX6UHwbBKxk dnI7/ZlOPW/6LNMn4aw/JW+kTi7CzJRDdox3J/C8aWOyurXUOGnR6sj8xuxKlAjK ivJVaag0TRRYENA9VQodA2wzOMUWAMCTPh6CXevnv577tAana3U+qAgS6IjH8V9G zJTsLf6m+wYjhAEyRDig9Ha/10Ty/kgtwmYo0lqU4UT60Zq5870by08j7vtODatk XtYzHGK88+59VHEQpNLBOiVCutPgTIVdYGC+UEtuwSqi5nOB4dRdMZxxm4kwqiEk pGgMfmG6WDrJCb2P4hkzkqcjDDobDt4WdjEzScqDqvJKWSmVncBJkDag+EkAuM2Q uKFq9By2xaQyDsQ4qqFd4AJl7srZ8l1m+Ge5HrCthflGQKYaJ21tQzlUQ7dhKJrl LvnwfSyIivFIcu+CY4vPqCZmtcyGpB9QWNycFLszn7A4mKNtfFpZCzWPKtu1dOn4 6dreVmZcZ0tBZgD9hytZtv1oQypEB+4A4foKV5jhdNciZ6/fJxBjFQ4pDf64M6Ic 6hDvhixWJSjQzQSDVcuJbDngmGDn5yKMEkwPr3nynlWfH/Ndwy/bEGc9hdqU2ZXh DIdAPzFAwAo7EXb6g39O =Pl9S -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Git merging fun and a local clone-per branch workflow
On 2012-03-24, Alexey Shein con...@gmail.com wrote: Hello, Just wanted to say that I updated multiple working dirs scenario here https://gist.github.com/2165086/, which is *much* more simplified now, thanks to dsp for hint about git-new-workdir script. It should work fine if all changes from downstream branches (such as PHP-5.3) are always merged into upstream (PHP-5.4). If it's not the case, then some other solution is needed. Can you pleae add a description like that to the php wiki ? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Git php-src Tags Renamed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Internals we renamed the tags in the git repository to php-X.Y.Zdev. This avoids an issue with current QA code. git pull origin --tags should give you the new tags. David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPbGD4AAoJEAT0aMuPE7Z1BN8QAJVerhzVhnQNC/klY4P9hGUX xllMAjBpBsb76ubY63d1Ssz9CKDigo7Y19YY3AV3NIs0PKyqCv6iDZ5T4Cj35gOJ +v4SNvcL4E3W+tB5PyXYkQCW5baY53Wf2GcU48X4uICjQYgO0nH/VyWFpTa3qyxJ MNB4QP2aryZX/ozOzhLarnkYXoYaoncwVqfet1/g4QKA/EKbhvv8XW77QuYYf951 UyefOAa9mKTOvlSY8I1LUz3ROrm1wZNFzQgMJyPLTzK6Jlt4osCkSB8PxjC9np8b 1vXejQZdH15r26haCzJxwjDTlWNDyFCYNaVgaKsUS6HyXMRD6i/A3mXrfvswmoYh BGGsFVJvuGkGxumVR6sEDwWAUzdtp+RXkGZkfNphWfvn+BQku0ZKj2TANd2PUmyw bzC8LBusjJkWxFcU4azslCEe6au5he4A0/5bsr5ExmWXG65t5Q+fv1qexFzC+huN fiEKrYxpWv6GB5BNTuqIE4qyfTscA1UIKDUQC8k409xt/2H1a7weh+YEMeMyGXfX hD/ONhV+ziLnPYiLk7HKs8fZGvwsBDvNM2hpJmoSP1G1TEN1rEo4ZIgCepv8FE5f qW0feEO5nxXYyoai/HJe+9lirO0bnyRy6O1AyKedsl2ggeqUo67NHX0k6mIKFeSO JDZikYhKthsyJPEc5qBL =2iQr -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: com php-src: Fixed reference counting: ext/spl/spl_directory.c
On 2012-03-22, Dmitry Stogov dmi...@php.net wrote: Commit:14af1fe6923c65a91cd77eab5a8d4326f854391d Author:Dmitry Stogov dmi...@zend.com Thu, 22 Mar 2012 14:38:38 +0400 Parents: 523396cb28a0cb87ced9ec1179ef4f119d28ec80 Branches: PHP-5.3 PHP-5.4 why are you commiting the patch 3 times? we have a defined workflow how to patch in git. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: com php-src: Fixed reference counting: ext/spl/spl_directory.c
On 2012-03-22, David Soria Parra d...@php.net wrote: On 2012-03-22, Dmitry Stogov dmi...@php.net wrote: Commit:14af1fe6923c65a91cd77eab5a8d4326f854391d Author:Dmitry Stogov dmi...@zend.com Thu, 22 Mar 2012 14:38:38 +0400 Parents: 523396cb28a0cb87ced9ec1179ef4f119d28ec80 Branches: PHP-5.3 PHP-5.4 why are you commiting the patch 3 times? we have a defined workflow how to patch in git. FYI: I reverted the changes on PHP-5.4 and master branch and merged the fix from the PHP-5.3 branch into PHP-5.4 and master. This way we can only refer to this particular change as revision 14af1fe6 This will help us to follow the described workflow at http://wiki.php.net/vcs/gitworkflow -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: com php-src: Fixed bug #61461 (missing checks around malloc() calls).: NEWS sapi/cli/php_cli_server.c
On 2012-03-21, Ilia Alshanetsky il...@php.net wrote: Commit:9dcfb8c73fd639485182497ae5a8fc7d7ca7eb11 Author:Ilia Alshanetsky ili...@php.net Tue, 20 Mar 2012 21:07:08 -0400 Parents: f3f76e5e8af265cd59d8edb7fb0827be6abc9a5a Branches: PHP-5.4 Please merge this into master in the future. I did the merge for now. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] ECDSA support in the openssl extension
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/21/2012 02:44 PM, Alexey Shein wrote: 21 марта 2012 г. 12:43 пользователь Sergey Ryazanov ryazanov@gmail.com написал: 21 марта 2012 г. 10:27 пользователь Alexey Shein con...@gmail.com написал: 21 марта 2012 г. 3:34 пользователь Sergey Ryazanov ryazanov@gmail.com написал: Hello all. Openssl starting from version 0.9.8 supports the ECDSA signature algorithm. Return value of the openssl_get_md_methods() also includes ecdsa-with-SHA1 string. But if I call openssl_sign() with EC key then I have an error: key type not supported in this PHP build!. After some time of digging I discover that this error is rises in the php_openssl_is_private_key() in the openssl.c file. This function simply don't includes check for EVP_PKEY_EC. All signature related actions are performed by OpenSSL library by self and don't depend on any internal code. Is any chance that EVP_PKEY_EC check would be added in the next release? Could I do something to speed up ECDSA adding process? Hello, Sergey, Best you can do is to open a bug with your question in bugtracker and send a patch fixing your problem (with test case attached) against php 5.4 branch. Now it's even easier since php-src has finally moved to git, so you can use github's pull requests mechanism, see https://wiki.php.net/vcs/gitworkflow#workflow_for_external_contributors for the workflow and https://wiki.php.net/vcs/gitfaq for general questions. Thank you for advice. I do so in couple of days. Btw is 5.3 branch in development state or only maintenance? If new feature could be added to the 5.3 branch. I preferred upgrade from 5.3.10 to 5.3.11 instead of 5.3.10 - 5.4. Can't say for sure, it's better ask maintainers, I've CC'ed David and Johannes. as long as it doesnt break any BC and only adds one constant I am fine with having it in 5.4.2. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPaedHAAoJEAT0aMuPE7Z1q3kP/0HbNS7cguw4AZW/B1iY3VJf /zHKomY12J5BFEQRHLxNzU2yTne40qyiLYlKB+VjBjXBXhgNKHUpUJKeR+kPjg6t SsqTDxsqYvmWVnb1TC073DmI4/+xKcTYCuNME85PgAvUmnhlw/Yhxc8XsNvOU5gb dmLTbh+vB5gQJu4aD67fQQWhPwrw29+riccYeZvPgAJ0AJKzl/e5RIC3WwqxRMbx kLVMkUY0237kTjq+DRc6/p/WKNGsfx67xyIOsaeBUObsQlFynGcC+89vuf2Og7QL qHMUIk4zf6UUEXNLDr4yp8n2E9cH65cgoxR1L9c2Nmz9Rwt/VxhJO94/fLHqmGBn kUA/JUnpKOWT+UozeVSj8PJNSTLkmkhRrilqD8vNLjDn2V7DECHUA6QpXN29Vzl4 UW4tUATBsSFnrn41nnVUQ3NV7vWacL0N0sxNcWbmkidIRdj8pp2sKLOhD0Ez9Ot/ WoaTNwGbij5CxWVpYCF2zXiw5Xkfl8MQeMwANMTlBeJZoMm3XYrx4zI93X5ld2Z+ meubAegmwxqwSMz6lflt1OKD8CC4wTJeuKrxzXecgkCX64pw3l7GQq/nKbFtrhoX Er1M8VqBL8IHzm2TCYNtWsQv2MEIn0O/nXhBFh2gxiqmcYyopbqy3pJTwoVif5qB eHsMSfDoDUxFkUgqKBJw =GNQS -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Github Pull Request
Hi with the php-src migrated to git we start receiving pull request on github. A few things to notice: - developers can pull the requests as described here: https://wiki.php.net/vcs/gitfaq#github_pull_requests - people with valid github accounts can comment on pull request - people with valid php accounts can close pull request using the tool http://qa.php.net/pulls. Thank you joahnnes for writing it. Before pulling make sure: - the pull request contains appropriate tests for the change - the commit message contains a good and precise description what was changed and why ensure that you pull it into the right branch. Pull request notifications are send to the git-pu...@lists.php.net mailinglist. Note that we DONT hand out access to the github repository and will we not add you to the PHP organization on github. - David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Github Pull Request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/20/2012 11:42 AM, Ferenc Kovacs wrote: I think it would be a good idea to explain why are we (not) doing that. AFAIR the reason is that if we hand out accounts on github, and somebody by mistake merges the pull request there (instead of pulling it to git.php.net, which will be automatically pushed to github) then our github-git.php.netclones will be out of sync, and that could/would be a PITA to fix. actually it will just be overwritten by the next push to git.php.net. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPaF9fAAoJEAT0aMuPE7Z1JlkP/jZwHXLnL+VQgUPcSG20APlS p8Hk5ieiILY1jR0qagugJQ17Jb8UVOPoAXdG4jSDS5qU4WavpYwwpMJ3G8HGXUyZ k/ctm8VY+7z2aAzfXytj+/vL4GhNapB832X390IBmb6A/Icv8uVMOnLaXvGBRTYd de//9H/Xglr4L2b99ulH0Ncqdgk9oRvkxcN6DgBU50H826lx19PIMsqGeNJzfP8n lmRITysgKQWwmwZzvGtEeFyeZw724GC+0TnW9hfeXRDEsF7tXJ+QrY0G12GD3abO 6uSoRfC/wBJe//FyVHcoYzAcKHIMWyORUVEKch3Kr0xlxpkm5cyVcwKjV++rELkr Mj3El8IidUZokYfiTSfTKagmCi6hxlS2y+bGO29CjlsFivgq7HQNc/QjckT8n/7p mrklNsHDO/Fr6AelxCQzpF8TjNVS0RXNdB/XtsenXfZE1Zm/TwIpguxmXtc+ipoW j1bCl0EdXM+3aM881CBnBhawzhrWjHcW5R+1yDOaRtk1mUs1W8ygIbLJRUXsCQkf A7jTScwtrD0A7S88mVDg90dyuwtpA8d/4vfCFaByK0vW2MOm8DvPhbsin0DKbGJc 9zsHA+NXpsclza27t9pIaTYt8zxkyQWmRNslJ3vXzwHgcPmCfEpSu0KL3pAj36NW ZjAhO77X0dafYTlwrWQA =1/la -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Github Pull Request
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/20/2012 06:29 PM, Kris Craig wrote: Quick clarification: On the other hand, by pull request are you simply referring to somebody else requesting that you pull their submission and merge/push it? If so, I get it, but I really think we should come up with another term to describe it because it really does sound kinda backwards IMHO. I just woke up less than an hour ago though so maybe I'm just groggy lol Drink a coffee wake up, think first and write the mail then and help reducing mailinglist noise by trying to figure it out yourself. We are referring to pull requests in the sense of pulling stuff from another repository into ours. We talk about pull requests made on github for the php/php-src repository. We use pull request the same way everyone else uses. Someone requests via github or a pull request mail (linux style) to pull his changes and merge them into our repository. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPaL+6AAoJEAT0aMuPE7Z1QUEP/0eHx5TWk3EI2Y7RZPoBPZlT 2/uxGtc0ofAu2Tk+xEt0Avhbxoy9+gwlsXsDZK2aTYd3lfHoHQJ9YJfcsbIH7vWi n08N0zI3uqeETyo/8W07KDIch6UGfEQaCgMDTDsAvIIJ7wLRCIYVuJEbAELdY1Xq egBOBxSuEFie2k4P0GPnw92P0vf5orvMRwnIrIks26/OnxEpBlvC/bR2JQbfbHSy qgJRP9KFV/rx8myvWPXhI6soNx1W8cuIiPgZY3ljslSjXJP5xiB88xzHIdnGk9KH 5q1H2XEZRt9TtLnOv0fxhvfgdPgxG2nD0UMo1Ucm/MJcDDaRA+hvlKpjNhAAx5qC K4+Jtt4er0Q9D3lZW+vYY4lfpmADrTIN2UylFqm/9K1Tyn3t3aZPo1R9xxLH9mtX JYRrZ2PZSWLdhQfZrPkJlVjkTZUCded/fEgr/3N4qjgoV+Yta4pw+XT1ccV8wMnG tUy2RBaZloIsRObQ/JUps1SURYjDLAku+1eaPKeCcgkJnhF7fDgm6BJyfqqXg9c6 ci/Pg0K69UtzbLNpThZefU6WHCHdUUZKU8/cea4NX1vnpzW1orsTxbFLtxfYlxUq eNTBQPeD7x0IGktF1uy5v+RGlpAEQQDgwEil3ovtjoNQ+XoAvDxeKtmhKzw0YmVF vltnqeQggRED7abRzXxR =W89T -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] php-src is now on git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/20/2012 09:48 PM, Ángel González wrote: El 19/03/12 21:29, David Soria Parra escribió: On 2012-03-19, Kris Craig kris.cr...@gmail.com wrote: The workflow page currently recommends the git: one for cloning (which doesn't work for me, either). git:// is recommended when you can use it. The access is limited due to port limiations, but the protocl itself is superior to https for the purpose. http is a fallback when you cannot use ssh (developers only) or git Actually, the provided url is wrong. It lists http://git.php.net/repository/php-src.git but that returns ERR access denied or repository not exported: /repository/php-src.git (that's an error given by the server) http://git.php.net/repository/php-src.git works for me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPaOxkAAoJEAT0aMuPE7Z1IUgP/imd9FqddUiAJcYnxjCFZB2T E+U0lkIy0w6zX0nVwgFsls47ON28tcQjblVmkwotpij+1IR70UuilOrjI3aaHHSx B0SyGUFMT7zoGAbs98tvwE2v26bYNd9fR15usZpLmnvyKoCZTXdJk8HRoyGpDQYm D3SsnPF1P11tyHPWcs5jVpemTbGY6EnGTRJbZbCZmSBTEwB9+DB+6BzXRHu8tNx2 nNfVlinnRvbw+VTvKbeYj3eThGmXCyztWyKNpnUW+oSS7CSA6uKaFUpDFZiaWgnd 9bGOe4evkKms8z3rJdE+mnoasTwxcTpT4XvaayEYShateKhozTWxQBE0ix7BuaMI WGkCuPhnko2fyTmhq5uxdpJL8/oxF8CejNcNCXGmi+8B1slIOXuk9owdI78g085f pGd6BSbjXfrhJnxAGLMwifY+aTVOSyr+nnlzuUIhJDsEWX5s77O4DQ1NmwJ7rDEU e1z0DbiL1enExipFi81H0r58J+05wPmbj4qIgZXstMhl/2qCoeCz9ZQ0z33QdEpC 5WGhShJjuiHWk7Vo/1oG1xObZ9qLefRPo7qq1D7eR7GmiCFKesCQX/VQtExkbtAR W3fOVPeoZMbaqW280iVqQsaeuV1TsQmkCG9WyjrnoL7kwGvPMr5T4hYYL4PGep8d Nd0JVzBlHgIINffgOc4p =0Uto -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] php-src is now on git
Hi Internals, The initial migration is done and initial testing was successful. http://git.php.net/?p=php-src.git;a=summary http://github.com/php/php-src Please note that some branches and tags were renamed to make the repository cleaner. Please checkout the repository and play around. I have created a workflow wiki page at https://wiki.php.net/vcs/gitworkflow. There is also an FAQ at https://wiki.php.net/vcs/gitfaq. If you have questions about the workflow or problems let me know. General git questions should be asked in the appropriate IRC channels and mailinglists. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] php-src is now on git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/19/2012 06:18 PM, Stas Malyshev wrote: Hi! The initial migration is done and initial testing was successful. Thanks David! This is awesome! Great work and I think it will make developing PHP and contributing to the project much easier. I think we should do php.net frontpage announcement. can someone do that? Please note that some branches and tags were renamed to make the repository cleaner. We need then to fix our docs on wiki - some of them say 5.4, some PHP_5_4. Also a small thing - gitfaq recommends git config core.autocrlf input, but we have some files in win32 which do not work with this setting (at least on my Mac). ah okay, can you remove it please? Thanks -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPZ2qvAAoJEAT0aMuPE7Z1e0sP/3gsDzHWhbb1YS+uwDQRfd/B jjuVy4eoBmfVXPZgLvCDRtLs1WzsmShfNQtI2jGr8ZZ9tTDrbLs624VZNXpoQudW SEFhyePPm/SRACFrpxLkAAd1vKrT+ZKUdpTjAgvK99lb29nbtYqwDp4S918+cGaP 3wlL5V0lacVL15cNs/mHZA3JE2wkvhyXVIVwnv8xjVxE7NE2NSfrkCJGlbYeJN8y uo5Yl9oa8uRzuYdi3NakvFJzqaNqxsrl299nk91kpY9eusyYR+elzUUik+yipp3H yhTie4/3HeNIbZM+g72BOfKFJoTKkkxvbLCKuuQwcUCHh0SBNnZeh27f7e0Yp+YX SjTY5GF3G3xtcC3/yLUR08/G7GCrwquwU350lk1Amjyb+5mSC1XFyAQ78/Cq9Sc8 itEwwqO1MjaQk7iE9KABqwb1M48ZZXlcfbO6Pz1RkShSuG1Uxy2Eb9crnii6bJJg RCNdJxf43p3lX1SLqP7mz0LXF1KQwpvueAN8I83BzprgYv/hT5zu8wII+frcJTWp NJKudPVHPS8viXKVSBDfQ5WGzCpfNKLQte4QpKZQ81aVeuyyXNjrKBgy6h2Wr20E KUE2JoUy6SjM7zL+1IeieYSsU3PKE+1nZXLmgPWWOyBjR2+oYX2aOLgIGKJJHJC9 A2PwEZR4kErUIBcAnoof =ngSq -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] php-src is now on git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/19/2012 06:16 PM, Simon Schick wrote: 2012/3/19 David Soria Parra d...@php.net: Hi, David Thanks for this great step! As I quickly viewed into the github-repository I recognized the big list of branches ... 52 is quite a big list .. I don't know if someone asked just that before: Are there plans reducing this list? Branches (at least to me) seems to be something like big features, bugfixes or releases that are or could actively be developed in the future. One step is for example closing all the php-4.x branches and leave them as tagged open-end if changes are not merged ... absolutly. We carrying around a lot of branches since 2001. Neither gwynne nor I wanted to remove the branches. People with full repository access are free to cleanup the branches and tags if they are sure that they are not longer needed. I personally dont think i am in the position to judge which branch or tag to delete and which not. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPZ2stAAoJEAT0aMuPE7Z1awoQAKLRXhY8BHbHoIbCmbO0vz/p 7LC5WdhiQ8HLp73HpmMf/jzS6D2+8nIOCKGi4cs1tht6nqG9IqKPZRTly+XY1Bu+ KOEysrbb1/OFBSl0B2ks+KiIrS5wVvWwkfHrNcEHsE/kdUdlRT73S3k5gkHN/fzo CLC0eZ+V/x6Tbd2Uf/nzS8ZM4b/2KdGnUCJw08nKsU5MmeUt85zTsRTAunaBzUQy cSiVCEFJ7TMyWTPGBECXtMu+dUJFlmjcLSRe7kFyZ1YHgX7b2WZHNi4OkLrAK5Kl ypFCr7wgHhTsR9/C3+ZzPD4BRJJvLfCWxHJz4qWl8j4fJ2SBLoHsvv/Q4alruhGY Z0D7HsySZgh1iCfDYXslzSY7HAkfUGLZtVh2L8ezPrCeZ+GO4aHMiQwsEbnq5G4Z NOxTR5HQBmyB2j+bc5Gsc63dxcDnySpBlmvh1XxZBYX1mSyLAlz/XzKsFpPTKOJr I4x8eA/qf449sCMr19+m3Evy6T6uGgzEwOKuer2+K086UIfbubL12hiS29Dj5IYN XjGcRFBHtCrGQXHNfSvMe+A3HRVCzx5Qu5UjjVm9L93+h2mn7Ix8e7bS9LAlMj3n KZ7SHCQGoL+WknYJOfr2YFurXUgM+3n4g/beXjVbHGE88IYTaS+7f5hUtIwLMHUM Ase72LeLJxIkN78pXCst =IPhy -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] php-src is now on git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/19/2012 06:20 PM, Derick Rethans wrote: On Mon, 19 Mar 2012, David Soria Parra wrote: There is also an FAQ at https://wiki.php.net/vcs/gitfaq. I can't find in the FAQ what's happening with the commit mails. Can you add that (and CC this list too)? (Refering to The git push/commit email notification process is under discussion (Jan 2012). For mail lists see http://php.net/mailing-lists.php; as well in the FAQ). I will add that. For every push a mail with a log what revisions are pushed will be mailed. For every commit in the push a follow up with changed files in the subject will be mailed too. The format should be: [git] branch PHP-5.4 updated. | [git] commit ab33e5176ae ext/lib/date cheers, Derick -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPZ2vOAAoJEAT0aMuPE7Z1LFAP/ja9A4mmyQbIpy69kKUEAcIh /XwxUF6R0xHdYsZ7JdKm7awiMIgxTYa0kdn3uvR0PREGt4MmPHIaO3Kaahg434tp 0zTbSlfnUKP3AyN1RdJ/gii23n6FHHC56qpKH+FdMQ6zVyNMWG6FczBypnL4w9uv /ucMsM9Y98jviL55mV2b/Gb7ZOHgBbi5sXSyY+iRRBXeV9JSclHppGwR7rfy7K+8 Qeuqce1aoEgKfNxUO6fGHOZYRD8AYOrdRNlOXT+sI0MzvbT+p5jW6t0Hlv4vczMY QTU2w28zr8ceyQYS4xghYMdqPcg/5+ogyGikGutVS38qBnnuJ1kT9VwR8L5zKFKo NZU54pbqbsr4J4aB+mMXETJ9kaOIEEJLvRxYlyzwVzq1XWNyKbhvGi9JX3BLyolU hgkYaWuzd77/ZjzY+JXUWpO+OIFQpjafZC8wxHEvhHRzslBfOBhdDSuub+vT15OD QBpyuBAe2VvJ2P3VwFJ1lzSNp/buiPp7mD1fPbRo5qibDm1sqkd8KPRGztQeggBH nx2UCsuCXKnnIRbsPiM9I37IVh1unYUv81myRmx96LYoH2o7guwQ44Ak8XmBPOKD gSkfJ6FQPEbvFCcQqJ6hiUZvzK0p9YJtMUEEBIDajQpDQMalQ7MfIa5ypQwnIZ1u WJAXVFsYkQO+57ySstva =k8nl -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] php-src is now on git
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [git] branch PHP-5.4 updated. | [git] commit ab33e5176ae ext/lib/date Can we strip out as much nonsense from there as possible? I am mostly interested in the short part of the commit message; and not the words commit, and the hash. we can strip [git] i personally think commit and the hash are necessary information but if people disagree we can change it. the current format shouldnt be a problem for the main purpose of filtering mails based on paths. I was mostly wondering where they are going to be sent to though.. PHP-CVS I hope? php-cvs cheers, Derick -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPZ20fAAoJEAT0aMuPE7Z1w/oP/0sLoQYAPM4dUCzX+fOU96Xy efiZccfsWfj8VZ5XUEUtA1dYYmGQeYt5TL+SLxdS//L2e6g7Ndi7ANcbDTDb+XGe W3/dLJxQbyksY773hr2kCWzMV5oZpbaqGKAj5jQlQnsNt6H54lyo0eY/JgaqY7YQ 2EhPHLGZiYRqZkcsjB09PqqyutJRLXkOd5ef6VjAlynZ+x6duC67zw/9LbYzGrSB Mmw7y8o7dqvs+fPJJXPvUBPOvu5hJP9hW0VJEIzMsq0i8lanhtfjVNelcfXACuMY U/SLSjdOoQTe/JNSVujTH8evZesLyuLKn/gs1XwY4nIl98Glhv/JSrq/RvC6lFAe ewghEOX7swr/VmSeFBwQ7miLGRn/dKD7d+FY+Ay6FaADXUx9KwGHhvdp1YLPvwnd C5/RrZFEC4fcnjwcJ68B/jhr4ZtRs0g/9WVZ4l1/8rWOviQqiEOrXgoELim+LYy3 yX0r8rmXICreuE0TaxBSS4VABsHk0guerT+XbB0TDysKyaMgE9RDx820A5aOPyUI BWLzDsibU8J5bJS81VetSbnq6YYWelxoCzsmFtRiSW+R1+xvu2rJeh7sWJYtwkc7 /FL2ftuQTysSUxb5zpXVt1F2MLQc62eonU4SBBvqY73PAZZ0jGHyiaJtrqLzI3qv WLelvoXKqgLCedNJkyDc =T/FL -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] php-src is now on git
On 2012-03-19, Kris Craig kris.cr...@gmail.com wrote: --f46d043892b5b345eb04bb9cfe02 Content-Type: text/plain; charset=ISO-8859-1 Hey Chris, On Mon, Mar 19, 2012 at 11:40 AM, Christopher Jones christopher.jo...@oracle.com wrote: I sense your hostility but I think you misunderstood my question. The workflow page currently recommends the git: one for cloning (which doesn't work for me, either). I think it should be changed to https://;, and I fully intend on making the change myself but first I wanted to ask here to make sure there wasn't a reason why they went with git: instead (i.e. I don't want to step on anybody's toes). git:// is recommended when you can use it. The access is limited due to port limiations, but the protocl itself is superior to https for the purpose. http is a fallback when you cannot use ssh (developers only) or git -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: [PHP-CVS] [git] commit php-src.git: UPGRADING
On 2012-03-19, Michael Wallner m...@php.net wrote: Shouldn't the commit mails reference the push mail? Looks a bit messy without relations of commit/push mails. they should, it's just not working yet. I will look into it. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Git Migration: Status Update for Todays Migration
Hi Internals, we will start migrating the php-src repository today and SVN access will be closed by 21:30 UTC. Thanks do Alexander Moskaliov we now have a much better, rewritten Mail script. Thanks to Florian Anderiasch we have a bugweb script. I added a wiki page for the workflow at http://wiki.php.net/vcs/gitworkflow. So far nobody has added questions to the gitfaq or the asked questions about the workflow (except for stas). Please let me know what you need to know to be able to work with git and I will try to clarify it as much as possible. Also, I would encourage people to contribute to the gitfaq and the gitworkflow page. Questions? David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Git Migration: Status Update for Todays Migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/18/2012 07:14 PM, Stefan Marr wrote: Hi David: On 18 Mar 2012, at 19:00, David Soria Parra wrote: Hi Internals, we will start migrating the php-src repository today and SVN access will be closed by 21:30 UTC. Thanks do Alexander Moskaliov we now have a much better, rewritten Mail script. Thanks to Florian Anderiasch we have a bugweb script. Thanks! I added a wiki page for the workflow at http://wiki.php.net/vcs/gitworkflow. So far nobody has added questions to the gitfaq or the asked questions about the workflow (except for stas). The workflow has one practical drawback over the current sparse checkout one. For me, switching branches also implies redoing configure and make, doesn't it? That adds quite a bit of overhead to build and test times. Yes. You can hover just clone locally (git will use hardlinks) and checkout different branches. Thus, I would suggest to document the workflow with different folders for the major branches. That would break all the merging mechanics and the branch semantics. Or, in case there is a better way, please let me know. Thanks Stefan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPZi3XAAoJEAT0aMuPE7Z1te4P/2Spbr4hKxnKa6IOuW62IRYC BqAxrxe+VsN7QBRAWF4eMan8cJjqfnHeX3BSc0gPiVfgZmZNdtrvvKEMK0yS5qmt KAyTRmA5BoxuZYHHBQ/29aM3fkaiv9q6GfJ7fto+8UMtuhgHgf0wHZtQgix/3Z5l I74Kc24JlryiRHerSLjRhxQu9fUoprb8ybsVTfrQaIbijag51l3qEN0kOX7yRKln c1FHNoLNeCn+M1k1TVn+2ocIBhAN2vlcCtgipgVzZLeD1rByjQVam+ChsU0z9jLt fX36rEZqQ3Oxbi6K/+qE2HvaQEZz3T2T0YExKlnD9ayQBXFqx7MRsvedm1jw/W20 IgQwWmIgFaCMX4I2uRscTvkOE1CrIsgFMgiX+lvJijeUgd8rYFT0h2BiWlbzoQYr ME7wGcFOMGep7/caSgMV5ckgSW00LEuQ8hxbshrK2R1afpTm0pivhcHwGwAQZ4iD RU9E8eOVbyJuGwTOEe9ou6X2IDG7kP0IUkV1js5StUq4szlyXYV6YvTRfrupx+H8 nRwSLO009Fv2Idp6WFWRb5iLqalXCjkNWJ3mrCMJiMRzrZ72w8v1Iz4Jr36aQvTW YuZce3wCTYdAeFwlZZPp1zavgZv1j+B9AOh3nSqLN6hzGjUuzhEQhAfPt+VfZf8W kDOs3hqcgxytV8mcT5GY =x4YU -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Git Migration: Status Update for Todays Migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/18/2012 07:31 PM, Derick Rethans wrote: David Soria Parra d...@php.net wrote: we will start migrating the php-src repository today and SVN access will be closed by 21:30 UTC. You'll leave it going read-only for a while I hope? I assume quite a few people have uncommitted patches. Absolutly. There is no plan to shutdown the server itself. Everything will be read only for at least this year. cheers, Derick -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPZi3+AAoJEAT0aMuPE7Z1WvkQALcaops48lLd+cJ3QYE8hs8n g0dlTxwX2smtBidi1X3IRPUMKX87hDZardM14OYY9CqqYokv+HbI5VsQoSeh4RsM 41Nn2cyYmsYLl1b+rCbDE6iL2CejtSxFbgUW5aYfWuUyyydocmGy1qxE/0aniSUN 5p+/hfpx36ZTF//adZHPNKpICkKFCW5pVzUfmi0MugllVRWUgqqfVlot/fOjg2Gp 4sJZqzj8s1c0V0cYnIFoSDrwr6NMzf2XqGHFodrYjnOuYjED3JokqC3Kr4Z8I1nA Yp+iVc7ZCIaZqaRuOC3hz2kzbLrTr4S6ZxUDG7bv/G0zxiVeL3JHie0wUK1hV63q MZ1aLaCnPVsmmTlwRs8pbVqmEMdSMjYZhZNeiU8oqK1ZpR0HqssvAZpJX9sw6P/E p0MhMWUFohTwy7xQZ+RYN702XFYuwzDh4gaElQXo8q0iN6eExwkjdxW1t2y7ZXmM QIhJ2Ws1E9GWEex9EopgXVn5LjUHx1pFU/6MFwbW43yGngmX34ycvaK4WKO01l6b ldRjOLYaTrxhWi78Zbs8QgZgRycOBu7yFzIFcR1d1MwEZFW1tGzaBNjAO6yi/+FL Zhaql8SVQXzw8SOmgGDAEN7s1TcU463NOvETdDx33+/mRwnoSGcq9aL7cMPVvXGU 4gCX+faMq5DZNC10xNaw =eF+M -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] HEADS UP: php-src is in read only mode
Migration is underway. Will take a while. Import takes a few hours. Expect git access to be available by Monday afternoon. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Git Migration delayed until Monday
Hi, I am sorry. I was ill in the last days and we some implementations were just finished. We have to delay the migration till Sunday 15. I am working workflow FAQ atm. David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Git Migration delayed until Sunday
On 2012-03-15, David Soria Parra d...@php.net wrote: Hi, I am sorry. I was ill in the last days and we some implementations were just finished. We have to delay the migration till Sunday 15. I am working workflow FAQ atm. oh god, that's a mess. It's Sunday 18. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Upgrade cURL extension
On 2012-03-10, Pierrick Charron pierr...@webstart.fr wrote: --047d7b2ee19338d79004bae668f3 Content-Type: text/plain; charset=ISO-8859-1 Hi all, As you may know, the cURL PHP extension is currently not in sync (featurewise) with the original libcurl. I started to work on it to make it as close as possible from the original libcurl. I also did some cleaning to make it easier to maintain (ordered all the constants/features by their libcurl version). All those changes were made on the trunk branch only. I wanted to make this new version available in PHP5.4 but unfortunately I did finish my work when it was already in RC phase. The question now is should we include this new version in PHP5.4.1 or should we wait for PHP 5.5/6/7 or whatever PHP next will be. There is no feature break (AFAIK) so all the previous code should work as expected. You'll find the list of new features attached and the last code in the trunk branch. Hi Pierrick, as long as your implementation does not contain crucial security fixes, I prefer not having it in 5.4 Let's try to keep 5.4 as stable as possible and minimize the amount of new code. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Re: Git Migration: Status Update
On 2012-03-07, Kris Craig kris.cr...@gmail.com wrote: --f46d044304ec4e135704baa12342 Content-Type: text/plain; charset=ISO-8859-1 On Tue, Mar 6, 2012 at 10:09 PM, Kiall Mac Innes ki...@managedit.ie wrote: On Wed, Mar 7, 2012 at 6:03 AM, Drak d...@zikula.org wrote: I know I keep promising to draft an RFC for this lol, so I'll make it a high priority to put together an RFC for a PHP Git branching model sometime this week[end]. There is no need for that. PHP will continue to use release branches with optional feature branches. We are doing one step at a time and have people adopt the changes slowly. We are after all a large project and a lot of contributors cannot spend hours of reading into a VCS and a new branching model. So we are slowly moving towards new models. After all I see no need to do it differently. You can use whatever branching model you want in your personal github repository and then send a final pull request that can be merged. Adding complexity to the main repository for no reason is not needed. Keep the complexity in your personal repositories. That is after all one of the main benefits of a decentralized version control system. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: HEADS UP: 5.4 branch is open again
On 2012-03-05, Matthew Weier O'Phinney weierophin...@php.net wrote: On 2012-03-02, David Soria Parra d...@php.net wrote: just a heads up. The PHP_5_4 branch is open for commits again. Related: With 5.4.0 out... how soon will the cutover to git occur? March 15. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DEV] Git Migration: Status Update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/04/2012 02:09 PM, Stefan Marr wrote: Hi David: On 03 Mar 2012, at 22:58, David Soria Parra wrote: (1) Pull requests on github.com go to the git-pull mailinglist. Make sure you subscribe to it. (2) Johannes is working on an interface that allows people with valid PHP user accounts to close pull requests. (2) Fix the bugsweb integration, so that references to bugs inside the commits will work. Florian is working on it. (4) FAQ Will there be an integration with pull requests and the bug tracker, or remains attaching patches the preferred way? Nobody has worked on that, but it's a possiblity. I would like to see pull requests supported in the bugtracker. What is the new preferred replacement for a sparse SVN checkout + single commit per change? As I understand it, currently, we try to have a single commit for all branches (PHP_5_n, and trunk). How is that supposed to be done with git? From reading https://wiki.php.net/rfc/dvcs#workflows, I assume, all branches need to receive separate commits + pushes? Sparse checkouts won't work anymore. The proposed workflow is: commit to the lower possible branch, then merge up to the other branches e.g: $ git checkout PHP_5_3 ..hackhack... $ git commit $ git checkout PHP_5_4 $ git merge PHP_5_3 $ git checkout master $ git merge PHP_5_4 There will be situations were we have to cherry pick certain changesets and then make sure that git doesn't get confused. David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPU9tNAAoJEAT0aMuPE7Z1sFcP/3Bc4AFhR0D78PDpovnflR8D KWRNyl6s1w6cwo1P98NhZzIJ9DuxKg0VAkU18YZamDpoghJScJe/W9YFu4xJLuZF oaw/4HhVxiQyi60i+eAADx9rAeanVRPVlBEjB4SOsAuj2Ax9Mx8gcfUHu37X+CiT sXOfL92lDDsHx9kJMM/mHkkXpyf5xfcgUatHoTNiBY7qkmznIvVEto8ohGmjsCbh GUQK5xbIqFzcmuN9uLnfMiDsppL+fFO05VHWJam8KmpoUQ4vNINZZp7zhpjGj5on PGi3Q/5jlAtJvK0utvqpfFbolk+d+54BN6YlnfNEsP/kageNIuR42qq/5SVm6qPa qyDcmrQp5kgyOAy2SwxFYZThEel46FBgu8LmCizh6n/sCgk9hFkg1GSH7lxNA4D5 FASiv1zYDVY2RpnxTyArUmgSdns+k6gXwc2gYZ6CcDJSzTg2jSPnyyjWjbKy5Edd k8NOHxM+GduvHpbQGO1uk2sk3TLY8inWHW22IVtIZ+kiXKPW2daJs8AcKeQqUSUe /mZQ3tci8XlWiaazWbcoU5Zw5iHNp/39BRWkJi2rHCNGFEqrcUOF8o4fo9Txjlwi 7h2vhcl00el1vS5k6vNQhrPd4a98uOc2AQQOJuwlAM2+xXgoxxuGPC0kAfP4n2+s zRsjMjOBD3ZCNypV8U0R =RgaM -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Re: Git Migration: Status Update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/04/2012 10:32 AM, Jaroslav Hanslik wrote: (3) Karma system fixes. Already done by me. People who have access to the root of a repository are able to do forced pushes. Do you think it's good idea not to forbid forced pushes at all? No. We will always need to be able to delete branches created, or tags (we had situations were we needed to retag, for example). That in itself can be used to do a forced push: git push :master git push mynewmaster:master Will be equal to git push +mynewmaster:master equal to git push --force mynewmaster:master I am also not a strong believer trying to forbid as much as possible. If you have an SVN account you are trusted enough to not just delete something that is used. Also thanks to the decentralized model of git we all have backups, so we can just recreate it. David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPU98AAAoJEAT0aMuPE7Z1SM8P/1eN+edqsqoMPukCZfeeWbFm DM4wRS1UYyc4WZ2LrUi/6+hadgEk4QZLwkLiZPw+CuYwlGtkRhIoPWskV3HK4xT9 HqdMeHxTxEAjsq0dnb37hklSGc2LlTFRnUhCHkrZdGb4OZEjOXeQBVa8ud/32Exa Cjxcyrmrzdxzu65W1P203zjAwo4jCR24PgWw4qhAqqI4UNYuHhgmIvptOo0MMvZV bkZ2GzKDsZladGG+mVwHdxZNwPOU9CxFnWG36wX7tl11uX80M+4WMTTJ43T1kpif ZhqbUrUWwitaZfdLBE9apKpwzO09cQdEsY7hgezZNntyH4PmHV+NCvCgz+BBywzM ivxNSjvTj8Kt3p4Y63WXOlfdrhTG/65hoZQTMn2Mv3qSIx3lVIqnUc/UFk5WBEI/ qOBARLGBtqy1ytMTdLLAcYN3cqFKS+zV0ucYIrBClr1LeIuAkIjfXNZ55CILmGy8 KEwJn6gC495jzV3LK7dw9S0mUiVvraG3IeBsNcJr8OELPZFC/U5IZHO0o1bafXWQ I/iqAA2tPeHQ289XyyHRSqL+qQHfDwP75gB0uUcu43lSieu0bNwkCI7IotHtC5vi dePV4pzyj+Yjyicx4NcrurWW5BeLafe8l1wvzUNS7SmrtUr3ZMJkj6qIVbVq6hq5 GvGw6+527FSIwn0TUGC2 =+P5T -END PGP SIGNATURE- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] Git Migration: Status Update
Hi Internals, with 5.4. out of the door, we can start thinking about moving the php-src repository to git. Commit access to the php-src SVN repository will be disabled on March 15. I will run the final migration on that date and push the php repository to git.php.net. Updates: (1) Pull requests on github.com go to the git-pull mailinglist. Make sure you subscribe to it. (2) Johannes is working on an interface that allows people with valid PHP user accounts to close pull requests. There are a few issues at the moment that we have to fix before: (1) Fix the commit mails to the proposed format. Irker is working on that. (2) Fix the bugsweb integration, so that references to bugs inside the commits will work. Florian is working on it. (3) Karma system fixes. Already done by me. People who have access to the root of a repository are able to do forced pushes. (4) FAQ Please send me questions about workflows, etc. I will try to answer them in the gitfaq to help you out with questions. We need to make sure people know how to commit, where to commit to, etc. I have the workflows in mind, but just not written it down so far. Feel free to help me. If you are not familiar with git, play with it now. We have a playground repository that everybody can use. Go ahead. I would love to see more and more pull requests coming in or patchs send with git format-patch + sendmail. Maintainer can apply those with git am. This helps maintainers as well as reducing the amount of new user accounts needed. So go ahead, send us patches! If you now a lot about git, feel free to answer questions on http://wiki.php.net/vcs/gitfaq and help out. If you have no clue about git and how to work on php from March 15 on write your questions down on http://wiki.php.net/vcs/gitfaq . David (@dsp_) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DEV] PHP 5.4.0 released!
Hello! The PHP Development Team would like to announce the immediate availability of PHP 5.4.0. This release is a major leap forward in the 5.x series, and includes a large number of new features and bug fixes. Release Announcement: http://www.php.net/releases/5_4_0.php Downloads:http://php.net/downloads.php#v5.4.0 ChangeLog:http://www.php.net/ChangeLog-5.php#5.4.0 regards, Stas and David -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
