MySQL Bugs: #16923: Bug in Date conversion

Bug #16923	Bug in Date conversion
Submitted:	31 Jan 2006 8:26	Modified:	31 Jan 2006 13:07
Reporter:	MySQL-Front Team	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.18	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
Please let me know if you are interessed to fix bugs - I will give you the detailed description after you fixed the critical bugs we reported before.

How to repeat:
Please let me know if you are interessed to fix bugs - I will give you the detailed description after you fixed the critical bugs we reported before.

Yes, we are interested in fixing bugs. Some of the bugs reported by you are already fixed, aren't they?

So, the question is: are you interested in submitting new bug reports? If you do, please, add more details about your date conversion problem.

After you fixed all critical bugs we reported we will give you the detailed description about this bug.

We're not interessed to investigate our time to describe a bug detailed while you don't be interessed to fix the more important bugs before.

If you confim that your are not interessed to fix the bug we reported we will stop infoming you about the next bugs we will find.

PS
I will not give you any further feedback before you confirm the fix of the other more important bugs.

Just search for the bug reports you sent at bugs.mysql.com, and you will see their current status. If you have further questions or comments about any of the bug reports you previously posted, please, add them to the reports. Or give URLs here and I'll try to figure out what's going on with that bugs.

Please feel free to take a look to each reported bug from us - also the closed bugs. You will find a lot of bugs without a confirmed fix of it.

After you fixed all critical (S1) bugs we reported we will write the detailed description of this bug.

It's up to you to show your interessts by fixing the bugs. Only the fix (or a confirmation of a fix) shows your interessts - your written words about your interesstions we learned are wrong. So there is no reason to trust your words.

Here you can find all the bugs we reported:
http://bugs.mysql.com/search.php?search_for=&limit=All&order_by=&direction=ASC&mine=233166...

So, most of bugs from that list (19 of 33) are closed. We have:

Bug #15943 is still being analyzed, bug #9934 - verified problem, not yet handled. All other your reports, besides this one, are either a duplicate of other known bug or not a bug (6 only, by the way). So, what is the problem?

> Bug #15943 is still being analyzed,

Please fix this bug before we write a detailed description of this bug.

> bug #9934 - verified problem, not yet handled.

Please fix this bug before we write a detailed description of this bug.

> not a bug (6 only, by the way).

At least one of them is a bug - but you are not able to understand the bug. 
Please fix this bug before we write a detailed description of this bug.

> So, what is the problem?

The problem is very simple:
You don't fix the reported bugs within a short time.

After you confirmed the fix of all S1 bugs we will write the detailed description of this bug.

So, what is YOUR problem?

OK, thank you for the clarification of your requirements. I hope we'll be able to meet them eventually...

By the way, people who want anything, including the bugs they found, to be fixed in any predictable time, usually just pay for the appropriate level of support. Then they demand the appropriate level of attention to their problems, from all employees of MySQL.

Bugs database is not for that. You inform about the bug, if you want. It will be fixed eventually, if you can demonstrate that it is a bug with a simple and repeatable test case. And even without this proof, it may be also fixed. Later, when somebody will have some more time to understand your report and the real problem.

This is how it works. MySQL contributes code to the community. Community contributes bug reports to MySQL. Without any obligations to each other. Just to make life better.

Since you don't know the detailed descriptions you can't decide that this is not a bug.

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.