Re: Fixes for documentation in source. Which branch to start?
| From: | Lester Caine | Date: | Thu, 18 Jul 2013 07:24:18 +0000 |
| Subject: | Re: Fixes for documentation in source. Which branch to start? | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-68147@lists.php.net to get a copy of this message | ||
Sherif Ramadan wrote:
It's a bit chicken and egg when it comes to the sample .ini files? Nobody should be installing a new server from 5.3, just perhaps rebuilding an existing one where their ini files should already exist? And if they are trying to replicate an older setup they already have the faulty details. In any case any changes would not be released until there was a security fix that warrants one? -- 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.ukWell, I don't see a good enough reason not to commit documentation to 5.3 as well I suppose you're right since it's not source code, but it remains dubious that this counts as documentation. If we want to add documentation notes for this it should go in the manual where we document everything. Not that I'm the arbiter of what goes in 5.3.5.3 is security fixes only.