Bug 112856 - MySQL 4.0 is out and considered to be in production state.
MySQL 4.0 is out and considered to be in production state.
Status: CLOSED DUPLICATE of bug 88437
Product: Fedora
Classification: Fedora
Component: mysql (Show other bugs)
1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Patrick Macdonald
David Lawrence
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-01-04 04:48 EST by Guðmundur D. H.
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 14:00:32 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Guðmundur D. H. 2004-01-04 04:48:21 EST
Description of problem:
MySQL 3.23.58-4 is being released with Fedora Core 1, and 3.23.58-5
(as of 4. Jan. 2004) is in Raw Hide, but MySQL 4.0 was released as
production long time ago. 

Having MySQL 4.0 would be nice, since it brings new nice features :-)

Version-Release number of selected component (if applicable):
3.23.58-4
Comment 1 shrek-m 2004-01-04 06:37:58 EST
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88437
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=89460
...

mysql-4.0.13 was in rawhide and was removed later.

http://www.redhat.com/archives/fedora-test-list/2003-July/msg00045.html
..................


imho it is to late for mysql-4.0.x
http://lists.mysql.com/announce/177

it should be at least:
mysql-4.1.1 (has been released)
http://lists.mysql.com/announce/175

or mysql-5.0.0 (has been released)
http://lists.mysql.com/announce/178
http://www.mysql.com/downloads/mysql-5.0.html


but i think that "fedora core 2" will come with 3.23.x  :-((
Comment 2 Guðmundur D. H. 2004-01-05 05:00:39 EST

*** This bug has been marked as a duplicate of 88437 ***
Comment 3 Red Hat Bugzilla 2006-02-21 14:00:32 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.