Releases for Drupal Automated Staging Toolkit

5.x-2.1
--------------------------------------------------------------------------------
Bug Fixes from previous releases
--------------------------------
1. FIXED: http://drupal.org/node/176240 The docs text files are now properly formatted - wrapped at 80 columns. I removed the duplicate installation section in README.txt and put a pointer to INSTALL.txt.

What's New
------------
1. The behaviour of DAST looking for properties files has changed for the better: instead of looking in DAST_HOME every time, by default properties files are looked up in the build file's ${project.basedir} property (set as the basedir attribute at the root element, if not specified defaults to '.') So you can run

./bin/dast -f mydir/myproject.xml

and the myproject.properties and myproject-base.properties file will be looked for in mydir instead of DAST_HOME; so you don't have to explicitly say -D"propertiesFile=mydir/myproject.properties"....

2. Added a -p or --project command-line parameter to help out with the long command-lines you need to use sometimes. If you have a myproject.xml build file and you put it in the directory DAST_HOME/projects/myproject you can now run from DAST_HOME

./bin/dast -p myproject

This is equivalent to:

./bin/dast -f ./projects/myproject -D"propertiesFile=
./projects/myproject/myproject.properties" -D"basePropertiesFile=
./projects/myproject/myproject-base.properties"

This is the third public release of DAST - the first after 5.x-2.0-soc07final. It contains major bug-fixes, feature
improvements, better documentation and other improvements over the 5.x-2.0-soc07final release, which this now supercedes.
The core of the toolkit for fetching, configuring, installiing, and patching a Drupal site has been completed. The four
core build-files slated for the 2.0 release are complete: site-fetch, site-configure, site-patch, and site-
install; and ready to be used by DAST end-users. All the required Phing tasks and types used in these core build files
are now complete and ready for use by DAST developers. The new Phing types for reading and writing directives and
sections to Apache .conf, PHP ini and MySQL .ini configuration files are complete. See the documentation home page for
an understanding of the design and implementation of this toolkit: http://docs.google.com/View?docid=dcgv33zb_25d26w5n.
The documentation page also has been updated withj with a lot more content. In addition, this release contains another
example project - there is a build project for creating a complete drupal.org clone site based on the drupalorg_testing profile.

This is the 0.2 release of DAST committed at the end of the evaluation period for SoC 2007. It contains several new pieces of functionality, most significantly, the ability to read/write Apache .conf and MySQL .ini files through the ApacheConf* and MySQLConf* Phing tasks and types. See the documentation page at http://docs.google.com/View?docid=dcgv33zb_25d26w5n for the full set of docs. Installation is the same as in 0.1 but be sure to get the updated dependencies package at http://www.abeharry.info/stuff/dast-deps.tar.gz or http://www.abeharry.info/stuff/dast-deps.zip

Minor update from 5.x-1.0:
1. added the tmp directory which is needed under DAST_HOME
2. Url to dast-deps packages had a typo
3. Added an INSTALL.txt.

This is the first public release of DAST - it contains one build script: dast-patch.xml. dast-patch automates the
process of setting up a clean Drupal site for testing patches. Specifiy the CVS revision of the Drupal core and
the modules you want, the target web directory and database, and the URL or filesystem path to the patch file
you want to test, and the dast-patch build script will delete the existing database and directory (if they exist,)
fetch the specified core and contrib- modules from CVS (or a local directory cache,) (re)create the specified Drupal
database and user, and download and patch the newly created Drupal install. It will also set the correct
$db_url in settings and autorun the Drupal installer to bootstrap the site - so all you have to do is continue the
install from the 'Choose site name...' page.

This is the first public release of DAST - it contains one build script: dast-patch.xml. dast-patch automates the
process of setting up a clean Drupal site for testing patches. Specifiy the CVS revision of the Drupal core and
the modules you want, the target web directory and database, and the URL or filesystem path to the patch file
you want to test, and the dast-patch build script will delete the existing database and directory (if they exist,)
fetch the specified core and contrib- modules from CVS (or a local directory cache,) (re)create the specified Drupal
database and user, and download and patch the newly created Drupal install. It will also set the correct
$db_url in settings and autorun the Drupal installer to bootstrap the site - so all you have to do is continue the
install from the 'Choose site name...' page.