[Kolab-devel] Kolab issue tracker situation

Jeroen van Meeuwen (Kolab Systems) vanmeeuwen at kolabsys.com
Wed Nov 9 17:32:32 CET 2011

On 2011-11-09 16:14, Thomas Koch wrote:
> Christoph Wickert:
>> If you read the instructions how to use the issue tracker you will 
>> see that
> If you read my mail, you will see that I just referred to open 
> issues, not
> only in the server. :-)
>> Roundup will be phased out, we are just not sure how to migrate the 
>> content
> Then please update all links to the new issue tracker or even better
> move the
> new issue tracker directly to issues.kolab.org and the old one to 
> another
> address. Otherwise people continue to fill issues in roundup.
> These sites reference issues.kolab.org:
> http://wiki.kolab.org/index.php/Kolab_Issue_Tracker
> http://kolab.org/
>> to Bugzilla. While I personally think this is a good opportunity to 
>> clean
>> the bug tracker (because a lot of bugs are no longer valid), others 
>> are
>> afraid that valuable information gets lost.
> Where's the problem? Just keep the old issue tracker living read-only
> and add a notice to all html sites referring to the new tracker. If 
> people want to
> continue working on old issues, they should re-open them in the new 
> tracker.
> After 2 years you should be able to pull the plug on the old tracker.

Hi Thomas,

I appreciate your passionate approach, but please remember things may 
not be as simple as they seem to be.

If it were just some one individual that would be able and was allowed 
to do as you describe, it would have happened already.

Kind regards,

Jeroen van Meeuwen

Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08

More information about the devel mailing list