I know that you developers are willing to help a lot with it, but that you
cannot manage to save the spare time needed to do it the right way. That's
why I would like to propose a simple/small/timeless change in your CVS
commit messages: If you feel that the change need to be documented, place
the @doc keyword at the end of your message log entry.
And if you feel like telling us more about what you changed, point us to
some online resource or whatever. Simply add that after the @doc tag. This
additional comment is optional, and you don't need to bother if the change
is obvious, or if you simply don't feel like doing it ATM.
This small @doc tag could _slightly_ improve/optimize/sanitize our work on
the documentation. By adding some SQL logging in loginfo.pl, and storing
the following:
bump, just to make sure this idea isn't forgot :)
It is pretty important to the doc team to have a list of commits that need
documentation. Currently I accomplish this by using my local inbox folder,
but this is not very efficient (nor shareable).
I don't program Perl for more than 5 years now, so I don't feel confortable
making those changes, so in the next step we need a volunteer to do it ;)
Nuno
P.S.: uhm, instead of changing the the loginfo.pl script we could have
either have a news.php.net crawler bot or an e-mail parser...
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
