-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

Dear all, re-sending without autocrypt option. There has been some reports of problems with SPAM filters discarding the previous email. If you already received the first message yesterday, please ignore this one and accept our apologies for the double sending. If you didn't get the original email, please read below.

Cheers Michele, Slavek

- --------------------

Dear all, we would like to explain the process of how bug reports get added to the next release bug list.

As many of you probably know, there are some bug reports (that we call meta bugs) that serve as an index for bugs to fix or already fixed for the next maintenance and minor release. For example bug 2247 for R14.1.0, bug 2696 for R14.0.5 and bug 2885 for R14.0.6. These meta bugs are intended to list bugs that have been selected by the developers for the mentioned coming release, so we would like to invite all of you to refrain from directly adding bugs to those lists on your own. Instead you should first discuss with one of the developers (say Tim, Slavek or Michele) and if agreed, you can then add the bug to the discussed list.

The reason for this logic (and limitation) is that if anyone just add bugs indiscriminately based on their own needs, those lists would grow out of control and out of what is physically possible to achieve with the development workforce that TDE has at the moment. We encourage all of you to participate in making TDE better, but please take note of the above procedure and try sticking to it as much as possible.

On a side note, R14.0.5 bug list has been frozen and no other bugs will go into it unless critical of blockers. Of course, if a working patch is provided before the release of R14.0.5, we will consider that for inclusion.

Feel free to provide your feedback on the process explain above

Cheers Michele, Slavek