Mailing List
Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
ODBC - ODBC with the MySQL Connector/ODBC driver
Perl - Perl support for MySQL with DBI and DBD::mysql
MySQL++ - Programming with the C++ API to MySQL
Subjects
• mysql openssl Question
• mysql:it 's a db not a dbms how it 's possible?!
• Does the binary log enabling affect the MySQL performances?
• Strange behavior, Table Level Permission
• FULLTEXT query format question
• Preventing Duplicate Entries
• Comparing and writing out BLOBS
• Executing MySQL Commands From Within C Program
• Can 't access mysql after kernel upgrade
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Downgrade Mysql from 4 to 3 23
• MySQL Cluster Software
• mysql test 4 1 fails with the gis test
• ERROR 2002: Can 't connect to local MySQL server through socket
• Getting Identity after INSERT
• Update one field with more fields from another table
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• mysql have same function mthod as Oracle decode()
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Production release of MySql 4.1

Production release of MySql 4.1

2004-07-01       - By Paul DuBois

 Back
Reply:     <<     11     12  

At 14:09 -0700 6/30/04, Jon Frisby wrote:
>As I understand it, the particular cycle a release is in depends on how long
>it 's been since a major bug was reported. So an alpha becomes a beta if
>nobody reports a major bug after N days, and a beta becomes a production
>release if goes N days without a major bug report. Thus, even if 4.1.3 is
>released as alpha, it could retroactively be declared beta, and then even

No, once a given version is released, it doesn 't get changed retroactively.
Either a 4.1.3a release would be done, or a 4.1.4 release would be done.

>release -- although that 's pretty unlikely. The long and short of it
>though, is that nobody can tell you how long until 4.1 will go beta.

Well, 4.1.3 has been announced today as a -beta release, so we all know
the answer to this now. :-)


>
>-JF
>
> > -- --Original Message-- --
> > From: Jonathan Soong [mailto:jon.soong@(protected)]
> > Sent: Tuesday, June 29, 2004 7:20 PM
> > To: Jocelyn Fournier
> > Cc: John Murphy; Emmanuel van der Meulen; mysql@(protected)
> > Subject: Re: Production release of MySql 4.1
> >
> > Jocelyn Fournier wrote:
> > > Hi,
> > >
> > > AFAIK 4.1.3 should be beta.
> > >
> >
> > It is a little frustrating,
> >
> > at Linux Conf Adelaide 2004 (January), the Mysql guy there
> > said that 4.1
> > would be in beta, in the next few weeks ...
> >
> > Its now July and its still in Alpha.
> >
> > It says on the webpage "MySQL 4.1 -- Alpha release (use this for new
> > development) " - and it has said that for 6months+
> >
> > So we did our development on 4.1, and were expecting it to be beta by
> > February 2004.
> >
> > We 're ready to roll it out as soon as it hits beta, i told my boss it
> > would be in beta by March 2004 at the latest. We now have hardware
> > sitting for around with 4.1 alpha on it that cannot be deployed.
> >
> > Does anyone actually have a concrete date when 4.1 will go into beta?
> >
> > Cheers
> >
> > Jon


--
Paul DuBois, MySQL Documentation Team
Madison, Wisconsin, USA
MySQL AB, www.mysql.com

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=mysql @(protected)