Fix #51: Fixed Issues are always set to Resolved status ...

Prior to this, whe plugin would always set a fixed issue's status to
Resolved, regardless of how the the "Resolve Fixed Issues" option
(plugin_Source_enable_resolving) is set in the config page.

Use Selection list to pick bugfix notes view state ...

To be consistent with MantisBT core, the bugnote view status is now set
by means of a selection list (i.e. pick public/private) instead of a
checkbox.

Added option to select view state of bug notes ...

Prior to this, the 'Bug fix' notes view state was hardcoded to public.
We are now allowing the administrator to choose whether they should be
public or private by means of a config option.

Fixes #42

Cyril's original commits were squashed.

Signed-off-by: Damien Regad <damien.regad@merckgroup.com>

Partial revert "Replace uses of config_get() by calls to plugin_config_get()" ...

This partially reverts commit 9222599.

It is required that we use config_get() referencing the 'Source' plugin
in SourceIntegration.php. Because SourceIntegration is a child plugin of
Source, plugin_config_get() does not refer to the correct config string
when retrieving the setting, causing 'Configuration option not found'
errors to occur.

Replace uses of config_get() by calls to plugin_config_get()

Simplify user-parsing code ...

Function Source_Parse_Users() was simplified by removing nearly
identical code to process the author and committer to a generic function
handling this task for both types of users.

Changesets store author's id instead of committer ...

When a commit is authored by A and committed by B, Source_Parse_Users()
function incorrectly sets A's id instead of B's as the committer,
resulting in incorrect changeset information being stored in the DB.

Fixes #44

Fix whitespace

Update copyrights

added support for Source/import by name

Implemented rough product matrix version/status integration

Initial UI for integrating Product Matrix versions

Touch last_updated when attaching changesets

Fix #145: Full import creates bad history entries

Fix #144: Proper changeset processing order ...

When commiting changesets that resolve an issue, the changeset data
should be saved to the database before beginning to modify the issue
data.  This is to fix a problem of generating an email with a change
history that did not show the attached changesets, which could be
confusing in certain cases.

Fix #131: Reversed history entry

Bug fixes for resolving commits

F/U 6999df13: Use proper repo object

Include repo name in history entries for clarity

Refactor loading changesets from database rows ...

This both simplifies the codebase by reducing duplication, and also
fixes a bug where the committer info was never loaded from the database
rows because the load_* methods had never been updated with the
appropriate row/property setters.

Reimplemented changeset linking; version increment

Added 6th commit note parameter for changeset ID

Implemented selectable fixed issue assignment

Fix #121: Configurable bug fixed status change

Fix #114: lingering t_bug_data

Re-licensed the project under the MIT license

Fix #96: Allow vcs integration configuration hooks

Fix #62: Remove pass-by-reference for PHP 5.3+

Fix #51: Improved commit post-processing events ...

Rather than having separated post-processing events for checkin versus
import, the post-processing has been moved to the API function for
processing commit data.

The first post-process event "commits" allows plugins to get a list of
all changesets as they are checked in or imported.  The second event
"fixed" allows plugins to see a list of bugs that have been resolved by
changesets, along with the appropriate changeset, as described by
feature request #51.

This commit also removes the postcommit/postimport actions from the
MantisSourcePlugin interface, as they were a deemed uneccesary with the
new implementation, and generally should not be needed for VCS support.

Update copyrights for 2010