On top of the aforementioned, there was a change in policy that a
change log for a particular release will now only be published when
the release becomes available for download. Also, the commits going to
the commits mailing list are now quite infrequent and mostly
It seems that the few things that were developed in a somewhat open
manner no longer exist. It would be nice to know what is going on. It
might be seem as a direct attack on whoever develops on top of the
On Thu, Aug 9, 2012 at 4:39 AM, MARK CALLAGHAN <mdcallag@stripped> wrote:
> If true this is also an issue for some users who don't modify MySQL
> source. They still want to confirm that bugs are fixed in new
> releases. Others want to confirm that binaries they compiled don't
> have any obvious bugs.
> On Thu, Aug 9, 2012 at 4:16 AM, Sergei Golubchik <serg@stripped> wrote:
>> Looking at the changes between mysql-5.5.25 and mysql-5.5.27,
>> I noticed that while it contains quite a few bug fixes, they all come
>> without test cases.
>> What would that be - a change in policy? Careless developers?
>> On the other hand, 5.5.27 contains a change to mysql-test-run to look
>> for test cases in the new directory, named "internal".
>> May be all new tests are there? That is, tests are no longer
>> Whatever the reason is - everyone, who modifies MySQL (all linux
>> distributions, facebook, twitter, taobao, and many others) have
>> just lost the ability to test their extensions.
>> Could anyone from Oracle shed some light on this?
>> Where did the new test cases go?
>> MySQL Internals Mailing List
>> For list archives: http://lists.mysql.com/internals
>> To unsubscribe: http://lists.mysql.com/internals
> Mark Callaghan
> MySQL Internals Mailing List
> For list archives: http://lists.mysql.com/internals
> To unsubscribe: http://lists.mysql.com/internals