[Kolab-devel] HOWTO: Block a Kolab release using Bugzilla

[Jeroen van Meeuwen (Kolab Systems)]

Hi there,

some of you may have noticed a large number of Bugzilla notification 
emails these days, which relates to our attempts to create some 
structure.

We could use your help, and so here's what we intend to do:

We have a guy sitting on top of so-called tracker bugs [1], and to make 
sure that we pay sufficient attention to the things we find important 
enough to get resolved before we pull the trigger on releasing Kolab 
3.3, normally all tickets that block this tracker bug should be 
resolved, released, verified and closed, *or* explicitly postponed.

If you find something that should be taken in to consideration for Kolab 
3.3 (which we plan to release sooner rather than later), please also 
consider blocking this tracker bug, by entering either its number (3341) 
or its alias (K3.3) in to the "Blocks" field of a new or already open 
ticket.

Please note that our time is limited (as is yours, I imagine), so we 
cannot make any guarantees -- but at least you'll have a chance we'll 
try ;-)

Kind regards,

Jeroen van Meeuwen

[1] https://issues.kolab.org/show_bug.cgi?id=k3.3

-- 
Systems Architect, Kolab Systems AG

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

pgp: 9342 BF08