COLLADA DOM release packages: Difference between revisions
New page: This page describes how to do a release of the DOM. This will likely only be useful for the DOM maintainers. In the commands below, I have the 'sfdom' env var set to https://collada-dom.s... |
m COLLADA DOM Release packages moved to COLLADA DOM release packages: oops, capitalization |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
==Tag the release== | ==Tag the release== | ||
svn copy $sfdom/trunk $sfdom/tags/2.0 -m "Tagging the 2.0 release of the DOM." | svn copy $sfdom/trunk $sfdom/tags/2.0 -m "Tagging the 2.0 release of the DOM." | ||
== | ==Build the release packages== | ||
We provide a Python script with the dom in the 'release' folder, called release.py. This script automates most of the process of building the binary and source zip files that will be put up on Sourceforge. Get the file by checking out the branch you're going to do a release from. For example, open up a shell and run: | |||
svn co $sfdom/tags/2.0 2.0 | |||
2.0/dom/release/release.py --help | |||
That will grab the release script and print instructions for how to use it. | |||
==Upload to Sourceforge== | |||
You have to copy the release packages to Sourceforge via ftp. [http://alexandria.wiki.sourceforge.net/File+Release+System+-+Offering+Files+for+Download Documentation] is available on Sourceforge. | |||
Once that's done you use the [http://sourceforge.net/project/admin/editpackages.php?group_id=157838 file release system] (requires admin rights) to manage the files you've uploaded. | |||
[[Category:COLLADA DOM]] | |||
Latest revision as of 23:21, 8 April 2008
This page describes how to do a release of the DOM. This will likely only be useful for the DOM maintainers.
In the commands below, I have the 'sfdom' env var set to https://collada-dom.svn.sourceforge.net/svnroot/collada-dom
Tag the release
svn copy $sfdom/trunk $sfdom/tags/2.0 -m "Tagging the 2.0 release of the DOM."
Build the release packages
We provide a Python script with the dom in the 'release' folder, called release.py. This script automates most of the process of building the binary and source zip files that will be put up on Sourceforge. Get the file by checking out the branch you're going to do a release from. For example, open up a shell and run:
svn co $sfdom/tags/2.0 2.0 2.0/dom/release/release.py --help
That will grab the release script and print instructions for how to use it.
Upload to Sourceforge
You have to copy the release packages to Sourceforge via ftp. Documentation is available on Sourceforge.
Once that's done you use the file release system (requires admin rights) to manage the files you've uploaded.