Take this with a grain of salt, but: On Thu, Jan 13, 2011 at 7:22 AM, Martin Scotta <martinsco...@gmail.com> wrote: > Hi all, > > I don't know how the internal development process of PHP works. > > First at all: was this feature approved?
>From my experience, don't consider something "approved" until it's in SVN, and even then maybe not (e.g. type hinting...), regardless of how many people say "I think that sounds like a good idea". > > if that is a "yes"... > is this feature going to be scheduled for some release? See below. > Is it supposed that I will submit a patch? Mostly, the burden is on the person requesting a feature to submit a patch, if for no other reason than that everyone is busy and that, as the requester, you probably have the most interest in getting the feature implemented. Once a patch is out there, you're going to need to convince at least one core dev to get behind your idea, since they are in the position of getting it into SVN, and they have the best big picture view of PHP. The core devs do often seem happy to help improve patches, if they think they're worthwhile. Then, perhaps it will get into SVN if a core dev likes it and no core devs oppose it too much. Then, perhaps it will be scheduled for a release. > > Thanks you all, > Martin Scotta > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
