project 6.x-1.0-alpha4

New features since version 6.x-1.0-alpha3

• #635892 by dww: Initial commit of the project_package module to track what items are included in package releases. At this point, it's just a database table populated by the packaging script, and Views support.
• #642106 by dww: Initial native support for a "Release type" vocabulary.
• #642110 by dww: Initial native support for a "Security update" term.
• #642112 by dww: Added a denormalized latest_security_release column to {project_release_supported_versions} to facilitate #642114, simplify queries, and to expose this information to Views.
• #642114 by dww: Compute and maintain the update status for every release node.
  • Added views support for the release update status code.
  • #645076 by dww: Properly set {prn}.update_status in the case of packages.
• #642096 by dww: Added a {project_release_nodes}.version_extra_weight column to provide a better mechanism for sorting releases with version_extra defined.
• #649254 by bdragon, dww: Added {project_release_nodes}.version_extra_delta since version_extra can't just be string sorted (e.g. beta9 vs beta10).
• #644258 by dww: Finished exposing {project_release_nodes} data to views. Views is definitely one of the things I'm thankful for today. ;)
• #644032 by hunmonk: refactor packaging script to get rid of stage one .make files and validation build key logic.
• #645712 by dww: Enhanced project_release_handler_field_files to allow custom file sorting and limiting the number of files displayed.
• #645866 by dww: Exposed {project_release_file} to Views for better UI of release file info when viewing release nodes.
• #645884 by dww: Improved the UI on package release nodes to display package contents in a more elegant way:
  • Major improvements to the update_status views field handler:
    • Can now conditionally include the recommended version for the release.
    • Can now conditionally include the icon directly in the field.
    • Can now customize the text displayed per status.
  • Fixed the project_package_items view to use the new power of this field.
  • Simplified the header over the embeded table to 'In this package'.
• #539682 by dww: Replaced hard-coded release download table with a view.
  • Added default view using recent release node views goodness
  • Split out the release into 3 tables, Recommended, Other, and Development, so that we don't have to clutter the table with text and icons about this, but can do so table-wide.
  • Paving the way for .tar.gz and .zip by being ready for N files.
  • Restored the pale green for recommended releases. ;) Switched to a better shade of red for dev/error to fit in better.
  • Slight tweaks to the release download table CSS
• #645074 by dww: Added a project_release_table views style plugin to handle conditional row coloring based on release update_status and to hide the update_status column on the project download table if empty.
• #647936 by dww: Only show the headers if there are more than 1 download table.
• #313827 by JoshuaRogers, dww: Made it possible to not recommend any branch.

Bugs fixed since version 6.x-1.0-alpha3

• #380814 by Damien Tournoud: Fixed duplicate entries in release history XML.
• #643528 by dww: Fixed PHP warnings on project_release_active_compatibility_tids when they're not defined (need an empty array, not empty string, for default).
• #685254 by boombatower, dww: Fixed PHP notices when various project-related taxonomy vocabularies have not yet been initialized.
• #645676 by dww: Fixed PHP notices in nodeapi() when releases are RSS items.
• #647426 by dww: Fixed the date in the project download tables to use the latest file timestamp, not the release node last edited timestamp.
• #649404 by hunmonk, dww: Fixed bug in an error recovery case. We shouldn't be testing for the youngest file in the directory and comparing to the tarball timestamp unless we're packaging a -dev that rebuilds. Otherwise, if we're repackaging a file that already has a tarball (e.g. to failed previously), we should overwrite the file.
• #649546 by dww: Cleaned up and fixed various problems in package-release-nodes.php:
  • Needless complication for calling project_release_check_supported_versions()
  • Named variables more friendly to pave way for .zip packaging (#11416)
  • Use the process id (pid) of the script invocation for the temp dir to avoid collisions
  • Fixed some bogus watchdog messages
• #698374 by bdragon: Fixed bug in project_release_check_supported_versions() for projects that use '0' for the major version in their releases.

Other changes since version 6.x-1.0-alpha3

• #642094 by dww: Moved the code to build the query that drives project_release_find_latest_releases() into a shared helper function,
  project_release_query_releases_by_branch().
• #645618 by dww: Added static caching to project_release_get_api_taxonomy() and project_release_get_release_type_vocabulary() since taxonomy_get_tree() doesn't cache for us.
• #683156 by bdragon, dww: Only prepend the opening xml tag when serving release history files if its not already there (prep for #683152).
• #683152 by bdragon, dww: Opening XML tag should be in the xml files, not in the serving logic (paves the way for serving static files).