maria-developers team mailing list archive

[Michael Widenius <monty@xxxxxxxxxxxx>]

Hi!

>>>>> "Vadim" == Vadim Tkachenko <vadim@xxxxxxxxxxx> writes:

Vadim> Guys,
Vadim> Let me say my vote here.

Vadim> I think it is critically important to have bugtracker that can be intergrade
Vadim> with third-part projects (patches, PBXT, XtraDB).
Vadim> I am asking to seriously reconsider and use Launchpad project. it may be not
Vadim> convenient in some ways, but it works.

We have internally just been discussing the possibility to use Eventum
for a bug tracker as we probably want to use Eventum for other things
internally in Monty Program Ab anyway.

The problem with the Launchpad bug system is that it's inferior in
many aspect to what for example MySQL's bug tracking systems is.
It's so much extra work that needs to be done to get to this level
that I don't think that the Launchpad developers will ever do it.

<cut>

>> > Ok, but I don't regard those two arguments (Bryan has time for it and
>> > others are asking for it) as a convincing argument for having MariaDB
>> > use this as a bugtracker. As I mentioned above, the bugtracking system
>> > at Launchpad works pretty well, integrated very well with the bzr
>> > branches, and so on. Considering MariaDB does interact with other
>> > projects for part of its codebase and other purposes, why not use
>> > something that already works rather than putting in extra?

Because the Launchpad system doesn't look like it will work when we
get lots of bug reports in different areas.  It's also very limited
in the number of fields, categories, bug solving steps etc.

>> > Look Monty, I like Eventum, Open Query uses it for some things also,
>> > but that's really not the issue here.
>> >
>> > If Launchpad bug tracking has some issues, we can identify them,
>> > report them, and see if they can be addressed.
>> > We know the people who build it and we know they're active and open to
>> > suggestions.

Don't think that will work.  For example, one could point to the MySQL
bug system and say that we would like to have all categories and all
fields that exists in the MySQL bug system. When this is done, then we
can start talking about the other features that doesn't exists.

>> > Just seems like a better way to use time and other resources, with a
>> > more satisfactory result for not just MariaDB but also others.
>> > Wheel-reinventing is terribly distracting and wasteful.

Agree that reinventing a wheel is a distraction. But so is trying to
use a square wheel and claim that 'it works for me so it should work
for you'.

>> I concur with Arjen here. The integration of the Launchpad Bug tracker with
>> Bazaar trees and other Launchpad features like the cross-referencing
>> between
>> other external bug trackers are very compelling. I've been using the
>> Launchpad
>> bug tracker for keeping a tab on the mylvmbackup bugs and I really like its
>> functionality. One nice feature for example is the way in which it searches
>> the database for existing reports when you start with your own bug report.
>> 
>> Also consider the user experience: they would have to learn yet another bug
>> reporting interface.
>> 
>> Keep it simple and don't reinvent the wheel, just because you can.
>> 
>> I was horrified when I learned that you have chosen to use the ugly and
>> collaboration-unfriendly WorkLog system again, instead of just utilizing
>> Lauchpad Blueprints...

Launchpad Blueprints can't be used as it lacks many of the features we
are using in worklog.

Actually, we are extending worklog to make it collaboration friendly
and it as far as I can see, it will be more collaboration friendly
that we could ever do with Launchpad.

Regards,
Monty