Hello everyone,
Soon the entire PHP project will throw itself into the fire and
migrate from CVS to SVN. This will break many activities here but the
task of editing EN DocBook files likely won't change much, except for
the commands to checkout/commit.
I'll be away July 9-13 but Hannes is leading the charge to unbreak
things this upcoming weekend. Please help. It's unfortunate the
project rushed into this (three day notice) but maybe we all needed
fire under our butts to get this done.
Our main problem is with translations because CVS Revision numbers are
required today and used with translations to track/sync with EN. I was
hoping the gettext/po effort would have gone smoother by now but it
hasn't. So, I ask that people think about solutions for how we handle
this, and determine if designing a system to instead use SVN revision
numbers should be done thus postponing our PO (or alternative) effort.
I don't like this but maybe it's where we're at, and maybe it must be
done. A simple system is possible although updating every translation
tool is a much larger task.
Other tasks:
- update euk2.php.net cronjobs to use SVN for doc.php.net and
docs.php.net
- update docweb crons and text
- grep phpdoc/scripts for cvs, determine which scripts we use, and
update
- update howto
- search wiki for cvs, and update
- grep phpdoc/en for cvs, update
- modify phd to say "...SVN Only..." instead of "...CVS Only..."
- reconsider text to say "VCS Only", "Not yet released", or something
that most understand
- ... what else?
Also, what does everyone think about a name change? I'm tired of
PHPDoc and phpdoc being mixed up so wonder if simply 'docs' would be
better and worth the trouble of changing.
Regards,
Philip
