The usual solution to this problem is to always code for things that exist. Then you have a relatively predictable coding path and relatively reliable testing tools.

In the best of circumstances, you have no control over when something will be sufficiently bug-free and reliable to move into production, or even (not speaking of MySQL here) that the implementation will be done in a way that is useful to you.

ari

At 03:00 PM 1/6/2004, you wrote:
Any chance that there's a quarterly strategic roadmap published
somewhere?

I have projects that sometimes depend on a feature in the next rev' or
some such, and I need to plan out for my organization... Difficult to
answer my boss when the dependencies are released "when they're ready."



-----Original Message-----
From: Tobias Asplund [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 06, 2004 5:25 AM
To: Allen Weeks
Cc: MySQL List
Subject: Re: MySQL 4.1 Production Release

On Mon, 5 Jan 2004, Allen Weeks wrote:
> Hi All,
>
> Just a quick question, does anyone have a good estimate of when ver
> 4.1 will go production.

When known bugs are fixed.
You can read up on MySQL's release policy here:
http://www.mysql.com/doc/en/Release_philosophy.html


-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to