I am aware that WordPress.org uses cron jobs to generate the nightly builds.
Something like:
30 23 * * * zip -r -9 ~/download/nightly-builds/wordpress-`date +%Y-%m-%d`.zip
wordpress/ ;
30 23 * * * tar czvf ~/download/nightly-builds/wordpress-`date +%Y-%m-%d`.tar.gz
wordpress/ ;
As merely a proposal (for testing purposes), perhaps it's worth adding:
mkdir ~/download/nightly-builds/testbed/wordpress-`date +%Y-%m-%d`
cp -R wordpress/ ~/download/nightly-builds/testbed/wordpress-`date +%Y-%m-%d`
cp /tmp/wp-settings.php ~/download/nightly-builds/testbed/wordpress-`date
+%Y-%m-%d`
This essentially retains a stack of WordPress installations where one can
check before-and-after effects 'in vivo'. The password can be given to
just a trusted group and changing of the password blocked.
Many find themselves downloading and installing new nightly build every
now and then. Others might file bug reports for already-resolved issues.
It seems as though it would be valuable seeing changes rapidly, merely by
running Wordpress off an open installation. CMS review sites give similar
types of access. This is by no means an alternative to downloads and in-
stallations in other sites, which are needed for more realistic and com-
prehensive tests.
Moreover, code could get re-used to give prospective users a live demo
rather than a screenshot gallery at wordpress.org.
Just a suggestion.
Roy
|
|
