thirdparty/README
author Todd Larsen <tlarsen@google.com>
Thu, 26 Feb 2009 04:29:56 +0000
changeset 1502 2fee94feef59
parent 153 79d52c2d50a2
permissions -rw-r--r--
Remove the release.py module and just use the field in app.yaml.template. This is a DRY fix, to have the release /branches/ and /tags/ use a release version that is compatible with the app.yaml file "version:" field. Also, the steps for creating a release were simplified (with several steps removed), and the release procedure moved to app/README, since app/soc/release.py is now deleted. Patch by: Todd Larsen Review by: to-be-reviewed

Third-party code that is *not* part of the application image (the Google App
Engine SDK in trunk/thirdparty/google_appengine, for example) belongs in
trunk/thirdparty.  For third-party code that *is* part of the application
image, see the notes in trunk/app/README.

== THIRD PARTY LICENSES ==

Third-party code must also include a license text file, named LICENSE or
COPYING, in the package subdirectory.  If the third-party package subdirectory
is maintained automatically with a tool such as svn_load_dirs.pl (which
removes files, such as license text files, that were added later to the
"target" directory), place the license text file in the trunk/app directory
and add the package name as a suffix.