CVS messages for Version Control / Project Node integration

June 1, 2009

• Commit #219186 by jpetso at 13:23
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_project.install 1.25
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_project.module 1.77

    Port of #371969 by dww, adapted and extended for cross-VCS purposes:
    Provide blocks for maintainer and developer commit information.

May 31, 2009

• Commit #218984 by jpetso at 17:32
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_project.install 1.24
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_project.module 1.76

    Block deltas are only varchar(32), so let's lose the 'versioncontrol_project_' prefix.
    (The module is stored in the block definition row anyways.)
    
    Hopefully, nobody has yet executed that update function.
    If someone did, just reconfigure your blocks please.

May 29, 2009

• Commit #218162 by jpetso at 16:22
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_project.module 1.75

    Implement the 'project_relation' constraint for versioncontrol_get_operation(),
    and adapt to latest API changes for statistics retrieval.

• Commit #218160 by jpetso at 16:21
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_project.install 1.23
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_project.module 1.74

    Have blocks use string deltas instead of integer deltas.

April 8, 2009

• Commit #194722 by jpetso at 22:37
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_release/scripts/package-release-nodes.php 1.11
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_release/versioncontrol_release.module 1.11

    Only alter forms and package tarballs if the project's VCS supports the
    functionality that is required for proper versioncontrol_release function.

• Commit #194606 by jpetso at 19:24
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_release/scripts/package-release-nodes.php 1.10

    Get rid of the last CVS dependency in the packaging script, by using
    the new versioncontrol_export_directory() instead of cvslib_export().
    
    The only thing left for mass compatibility is disabling VCS-based release
    functionality for backends that don't implement the required functions.

April 3, 2009

• Commit #192594 by jpetso at 22:08
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_project.module 1.73

    Adapting to API update: versioncontrol_is_account_authorized() has swapped parameters.

March 21, 2009

• Commit #186450 by jpetso at 02:33
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_project.module 1.72

    Bug fixing time. (Hat tip: PHP notices.)

• Commit #186448 by jpetso at 02:32
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_release/versioncontrol_release.module 1.10

    Use versioncontrol_get_parallel_items() instead of a pure database query.
    That causes a CVS invocation every time a release node is edited,
    and in turn, decreases the database load a bit.
    
    Most importantly though, the branch/tag selection will now work correctly
    without complex database-dependent handling of which labels are currently
    available and which ones are not.

March 9, 2009

• Commit #180796 by jpetso at 04:46
  Version Control / Project Node integration: /modules/versioncontrol_project/versioncontrol_release/versioncontrol_release.module 1.9

    Also disallow to delete a release file when version control integration
    is enabled for the project. Now looks like on drupal.org for the file part.