Bug #55197 [Opn->Nab]: required validation

Edit report at https://bugs.php.net/bug.php?id=55197&edit=1 ID: 55197 Updated by: yannick@php.net Reported by: philip@php.net Summary: required validation -Status: Open +Status: Not a bug Type: Bug Package: Online Doc Editor problem Operating System: Irrelevant PHP Version: Irrelevant Block user comment: N Private report: N New Comment: Thank you for taking the time to report a problem with PHP. Unfortunately you are not using a current version of PHP -- the problem might already be fixed. Please download a new PHP version from http://www.php.net/downloads.php If you are able to reproduce the bug with one of the latest versions of PHP, please change the PHP version on this bug report to the version you tested and change the status back to "Open". Again, thank you for your continued support of PHP. Too old ;) Best, Yannick Previous Comments: ------------------------------------------------------------------------ [2017-09-21 15:29:22] cmb@php.net Ah, well, this is about PhDOE. I'm always running configure after having committed several patches, and updated my SVN checkout, and I suggest others do so as well. ------------------------------------------------------------------------ [2017-09-21 15:27:22] cmb@php.net > People are creating invalid patches, which are patches that break the build. > Then, people commit them without first running configure.php In my opinion, a failing build is less severe than anybody committing nonsense (e.g. wrong information, gibberish) which successfully builds. And if a build fails, it might be sufficient to point the committer to <http://doc.php.net/tutorial/editing.php>, particularly the section "Validating your changes". ------------------------------------------------------------------------ [2011-07-16 09:34:18] philip@php.net I don't think we need another machine doing that. The edit.php.net machine checks builds for each translation and sends emails daily when a build is broken, but there appears to be a bug that is preventing or interfering with that now. However, the intent of this bug report (feature request?) is to prevent the broken build in the first place. ------------------------------------------------------------------------ [2011-07-14 05:46:49] rquadling@php.net http://oti1.php.net/logs and http://oti1.php.net/logs/build.chms.log shows the current log files. ------------------------------------------------------------------------ [2011-07-14 05:45:49] rquadling@php.net Just to add a little weight to this, and specifically for translators, of the 10 translations, currently 5 have failed to pass configure.php. So no new Windows CHMs this week. Would a "continuous integration" mechanism be suitable. As I understand things, all of the PhD outputs can be built on Windows, and as Windows is required for the CHM and EnhancedCHM builds, it would seem suitable to do it all on one machine. Would constantly building, or at least daily building, with emailed reports for failures only (though no news is assumed to be good news - so maybe report every build) be a viable solution? I was thinking something along the lines of http://windows.php.net/downloads/snaps/php-trunk/ but for phpdoc. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=55197 -- Edit this bug report at https://bugs.php.net/bug.php?id=55197&edit=1