taxonomy vocabularies have not yet been initialized.

since version_extra can't just be string sorted (e.g. beta9 vs beta10).

that caused it not to save the correct status in cases where a release
was stored in the DB as out-of-date but it is now the current release.

for projects that use '0' for the major version in their releases.

not in the serving logic (paves the way for serving static files).

release history files if its not already there (prep for #683152).

field handler to gracefully fail if there are no results in the view.

This change requires Views 6.x-2.8.

- Needless complication for calling project_release_check_supported_versions()
- Named variables more friendly to pave way for .zip packaging (#11416)
- Use the pid of the script invocation for the temp dir to avoid collisions
- Fixed some bogus watchdog messages

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.

the latest file timestamp, not the release node last edited timestamp.

handle conditional row coloring based on release update_status and to
hide the update_status column on the project download table if empty.

Switched to a better shade of red for dev/error to fit in better.

= 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'.

sections added to the release node in project_release_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.

package contents in a more elegant way. Not complete, but a lot better.

of release file info when viewing release nodes.

custom file sorting and limiting the number of files displayed.

field in the {project_release_nodes} table:
- Since the value is already denormalized, there's no need for the
  wonky taxonomy filter stuff, we can use a custom in_operator filter
  to directly work with the tids. This also supports putting the
  filter into a mode where it always operates on all active terms.
- Added a trivial field handler to render the values from the
  project_release_get_api_taxonomy() tree.

and project_release_get_release_type_vocabulary() since taxonomy_get_tree()
doesn't cache for us.

the denormalized version_api_tid field. Also, there's no reason to
define 'group' for every field since we already defined the group on
the whole {project_release_nodes} table.

print the recommended release for each project in a given package.

what items are included in package releases. At this point, it's just
a database table populated by the packaging script, and Views support.

#640916 by hunmonk, adrian, dww: Clean up drush_make.do.drush.inc, and find it a home. goodbye, drush_make_d_o.drush.inc -- your stay was brief by meaningful ;\)

#644032 by hunmonk: refactor packaging script to get rid of stage one .make files and validation build key logic.

project_release_compute_update_status().

Views is definitely one of the things I'm thankful for today. ;)