- Skip node entity cache when calling drush vcpi-git-resync-maps.
- Insert values in chunks instead of in one block.

This is implemented via:

- A new versioncontrol views_set plugin, project_issue_operations_view,
  which refer to a versioncontrol operations block view with a vc_op_id
  contextual filter accepting multiple values.
- A new versioncontrol_project_issue block, vcpi_operations, which based
  on the current node, renders the new view_set.
- A new default view, vcpi_related_operations, for the
  project_issue_operations_view views_set.

Issue #493074: Added an event processor git specific plugin to back-link to the commit as a comment on the related issue.

Issue #443000 follow-up: Support pushing the same commit to other branch on git_issue_mapper plugin.

- Provides a versioncontrol event processor plugin, which do the
  matching.
- Implements hook_versioncontrol_repository_{pre,post}_resync() doing a
  best effort to maintain existing mappings based on git commit hashes.
- Provides a drush command, vc-project-issue-git-resync-maps, to
  re-synchronize mappings based on project or repository ids.

Issue #443000: Added a new module to store the relation between versioncontrol operations and project issues.

- Maintains the table with the relations.
- Implements hook_node_{update,delete}().
  hook_versioncontrol_entity_commit_delete() and
  hook_versioncontrol_repository_bypassing_purge() trying to keep data
  consistent.
- Adds the versioncontrol operation objects on the project issue nodes
  via hook_node_load().

Since many sites (including Drupal.org) need custom logic for parsing
VCS labels and mapping those to the version subfields (e.g. to know
that '7.24' should be version_major: 7, version_minor: NULL and
version_patch: 24), we want to define all the version subfields
directly when altering the release node form. See also [#2145667].

If versioncontrol_release is enabled, don't assume there's an API
compatibility vocabulary defined and generate PHP warnings.

While testing on a local site for a release node created via a Git tag
with a version_extra element, I discovered that the default label to
version mapper plugin was broken and inspecting a non-existent
variable to find the version_extra string.

Issue #2127373 by jthorson, marvil07: Better checking of release files on release node edit form alter.

Jeremy Thorson authored Aug 25, 2013 and Marco Villegas committed Aug 25, 2013

Issue #2073487 by jthorson: Fixed drupalorg_versioncontrol: Attempt to clone a non-existent project causes an array_flip() watchdog notice.

- Re-build based on versioncontrol_project vc_project_user_commits view
  to use views 3 API.
- Feed display now relies on provided views plugin. See
  http://drupal.org/node/1465306 for details.
- Also moved to versioncontrol_project_git module.

- Re-build based on versioncontrol_project vc_project_global_commits
  view to use views 3 API.
- Feed display now relies on provided views plugin. See
  http://drupal.org/node/1465306 for details.
- Also moved to versioncontrol_project_git module.

- Re-build based on versioncontrol's vc_project_commit_view view to use
  views 3 API.
- Feed display now relies on provided views plugin. See
  http://drupal.org/node/1465306 for details.

- Re-build based on versioncontrol's commitlog_user_commits view to use
  views 3 API.
- Feed display now relies on provided views plugin. See
  http://drupal.org/node/1465306 for details.

- Re-build based on versioncontrol's commitlog_global_commits view to use views 3 API.
- Feed display now relies on provided views plugin. See
  http://drupal.org/node/1465306 for details.

- Re-build based on versioncontrol's commitlog_global_commits view to
  use views 3 API.
- Feed display now relies on provided views plugin. See
  http://drupal.org/node/1465306 for details.