On Wed, Mar 31, 2010 at 17:55, Philip Olson <phi...@roshambo.org> wrote: > On Mar 31, 2010, at 7:48 AM, Adam Harvey wrote: > >> On 31 March 2010 22:25, Christopher Jones <christopher.jo...@oracle.com> >> wrote: >>> It's not clear if/how these features are going to be re-included. >>> >>> I'd prefer to see them commented out. Displaying mis-information is >>> harmful to the overall PHP project. >> >> Agreed. We can always reincorporate documentation for any features >> that are backported to the new 5.3-based trunk, but since most of them >> are going to be Unicode-related, I don't think there's any need to >> keep them user-visible for now. > > Great feedback everyone! Replying to all here: > > - The word Next. Next (or NG) implies the next release, whatever that might > be. Although likely true, this feels misleading. > - Trunk. Not everyone knows what SVN is, much less Trunk. We could > link/teach but ...
We already say (with version info) "May only be in SVN". That could change into "Only in development releases" or whatever. We already have an unwritten policy for this, so please be consistent. > - Commenting out stuff. Sounds reasonable. We use FIXME in several places, > and will do so here too. I think this is the best choice. The status of merging things back from that branch in unclear. Do note: Don't use general "FIXME" for this, use a specific "FIXME OLDPHP6" comment or something that can easily be grepped for. > - Rewording. Reasonable for some cases, e.g. "Magic quotes are deprecated > and will be removed from PHP in the next major release." Even the "major release" statement is unclear. PHP5.3 was a *major* release, just not a "major release version bump"... :) I recommend "Magic quotes are *deprecated* and *will* be removed in the future", making "*will* be removed in the future" an entity which can be replaced with additional text + version number when it comes to it. -Hannes
