Provide blocks for maintainer and developer commit information.

(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.

and adapt to latest API changes for statistics retrieval.

functionality that is required for proper versioncontrol_release function.

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.

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.

is enabled for the project. Now looks like on drupal.org for the file part.

anymore, it's not required by any code in the module. That function was
conceptually wrong anyways (at the very least, it could never really be
written in a sensible default way that is website independent), so let's
get rid of it altogether.

I think it's alright now.

prevent users from adding a release node from a branch that has the same
version string as an existing release node from HEAD. Removing the code
that disables the validation would help.

conversion algorighm.

d.o core, we want to use that instead of the $_SESSION['not_slavesafe'] hack.

bootstrapped, in order to make node_load() more robust.

Also, fix retrieving the release node's nid as I previously changed its
alias name in the query. Makes node_load() (and other queries) work at all.

Also, convert the "cvs export" code to cvslib_export(), as an intermediary
step before going versioncontrol_export_directory() full way.

Move the implementation of hook_project_issue_assignees() out of
drupalorg.module into versioncontrol_project where it really belongs. All
users with commit access to a project can now assign issues to each other.

version control integration, similar to project_use_cvs() (only better).

Also, have the settings page item's description say what it actually does,
and fix grammar in the copyright header.

Use node_save() instead of UPDATE {node} in the packaging script.

    easier to factor out eventually.
* Remove the "!$is_core" condition for $is_contrib as it's always true
    with different repo_id values.

initialize the theme system. A few weeks ago, merlinofchaos persuaded me
that even with this hack, some Drupal functionality might still break.
So we should try to avoid chdir'ing at all cost wherever possible.

As the package release script now stays chdir'd inside $drupal_root
all the time (...well, most of the time) we can get rid of that hack.

    I finally understand now how this stuff works :)
* Display the admin-defined release node creation message
    after inserting a release node.

* Split out configuration variables into a file that is not
    version controlled (and only supplied as .example.inc file).
* Improve stderr output.

Adding copyright for the people that contributed non-trivial improvements
to package-release-nodes.php from project_release, determined by a review
of that file's CVS log.

package-release-nodes.php script to Version Control API.

Still works with CVS only, but already removes a couple of hardcoded
drupal.org specific assumptions, to the point where it might even work
with non-d.o sites. In time, we should try to get these d.o customizations
out into site-specific code like the drupalorg module.

Completely untested at the moment, though.
I wouldn't be surprised if it even contains trivial syntax errors.

without relying on project_release's CVS-centric 'tag' property.

Doesn't quite work perfectly yet, but it's a good start.

Also, a few cosmetic updates in the file header comments.

already exists, which happens for branch and tag operations.
Those project/* associations should really work correctly now, I think.

* Fix the item query for updating project/item associations when the
  project directory changes - it didn't include the repo_id, which is baad.
* Move hook_enable() to versioncontrol_project.install, as it isn't
  executed in when residing in the .module file.
* Use commitlog_operations_page() instead of commitlog_operations() so that
  query argument filters work also on node/$nid/commitlog.

Still comes without directly hooking into the versioncontrol_get_operations()
query, but even without that we can already cut down a lot on queries.

Lose two API calls (get_statistics() and get_projects_for_operation())
in favor of lower-level code (direct queries or new constraints for
versioncontrol_project_get_projects()).

Also fix the user account page's project/commit display to work again.

To the best of my knowledge, the project node integration module should
now work correctly again, and more efficiently than ever before.
Further performance improvements ('project_nids' constraint for
versioncontrol_get_operations()) pending.

do mention it specifically with a drupal_set_title() call too.
Cherrypicking from dww's commit 167900.

and fix at least part of the project edit form too.

$form['blah'] = array('#type' => 'value', '#value' => $blah);
elements with
$form['#blah'] = $blah;
as the former is now deprecated in Drupal 6.

I hope I didn't miss any form_alter or $form_state['values'] conversion,
anyways I tried to be as thorough as possible.

Did not touch the form_altered node form, as it's supposed to have changed
in regards to form element handling, $form['#node'] and all. This will need
to be tested and probably fixed sooner or later.

and get rid of the D5 one.