-
Notifications
You must be signed in to change notification settings - Fork 149
README For A Perfect Release
Update the version into the following files:
runtime/lib/Propel.php
generator/default.properties
Use git log --pretty="%h %s"
to generate the CHANGELOG
content.
You should remove all Merge ...
messages as they are useless.
Then, commit these files + the CHANGELOG
file. The commit message should look like Prepare X.Y.Z release
.
Tag a version X.Y.Z
.
Push!
Assuming you've just tagged a new version of Propel X.Y.Z
.
First, SSH into the Propel server:
Then get it:
git clone git://github.com/propelorm/Propel.git
cd Propel
git checkout X.Y.Z
cd ..
cd files.propelorm.org/public_html/
wget https://github.com/propelorm/Propel/zipball/X.Y.Z
wget https://github.com/propelorm/Propel/tarball/X.Y.Z
cd ../..
cd xsd.propelorm.org/public_html/X.Y/
wget https://raw.github.com/propelorm/Propel/master/generator/resources/xsd/custom_datatypes.xsd
wget https://raw.github.com/propelorm/Propel/master/generator/resources/xsd/database.xsd
Generate the documentation into: https://github.com/propelorm/api.propelorm.org.
Create the two PEAR packages (generator/runtime) and use the interface to upload them (pear.propelorm.org).
In order to generate the Propel packages, you MUST:
- have a working PEAR installation, use http://pear.php.net/go-pear.phar to get ready;
- discover the PEAR Propel channel by running
pear channel-discover pear.propelorm.org
before everything else;
Now, you can run the following commands:
./vendor/bin/phing -f generator/pear/build-pear-package.xml
./vendor/bin/phing -f runtime/pear/build-pear-package.xml
You get two packages (.tgz
) in generator/pear/build/
and runtime/pear/build/
. Upload them.