The source integration one makes sense to include [as we used to include old style integration].

Only thing I'm concerned about is whether we can version it if we use git submodules. We need to be able to pull out a copy of mantis from git with the exact version in any branch at any time. Does the submodule git functionality do this, or is this where we need to look at the subtrees thing/something else?

On Sun, Oct 13, 2013 at 8:22 PM, Victor Boctor <> wrote:
It makes sense to examine the list of plugins and determine which ones may be worth inclusion into the core product or as core plugins.

I'm suggesting that we include "source integration" plugin as a core plugin that is included in master branch as a sub-module.  That makes the functionality available out of the box.  The manual should also be revised (as necessary) to cover the usage of the plugin.

There are other ideas that make sense to include, though I'm not sure of their readiness:

- Event Log - I've implemented this sometime ago and haven't tested it recently.  The goal was to provide an easy way for admins to see the logging information.  And also act as a system wide audit.

- Paste Image - that is great functionality that makes sense to include in core product.  However, I haven't tested it and I'm not sure of its compatibility with browsers / graceful degradation.  I think that's a piece of functionality to keep an eye on.

The one that I'm suggesting right now is the source control integration.  Others, we can work on to make them ready for future releases or v1.3.



October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
mantisbt-dev mailing list