MySQL patches by Codership

timeline

18 of 8 results
5.6 series Focus of Development
Latest milestones: 5.6.17-25.6     Latest releases: 5.6.16-25.5, 5.6.15-25.2, 5.6.14-25.1, 5.6.13-24.0-beta
Bugs targeted: 32 New, 3 Invalid, 1 Won't Fix, 17 Confirmed, 4 In Progress, 7 Fix Committed, 170 Fix Released
Blueprints targeted: None

The wsrep replication API patches for MySQL 5.6 series

Bugs targeted: 33 New, 2 Incomplete (without response), 5 Invalid, 2 Won't Fix, 11 Confirmed, 4 In Progress, 35 Fix Committed, 439 Fix Released
Blueprints targeted: None

This is a series for MySQL-5.5 wsrep patch

5.1 series Active Development
Latest milestones: 5.1.63-23.5     Latest releases: 5.1.62-23.4, 5.1.61-23.3, 5.1.59-22.2, 5.1.58-21.1
Bugs targeted: 5 New, 2 Invalid, 6 Won't Fix, 4 Confirmed, 1 In Progress, 8 Fix Committed, 66 Fix Released
Blueprints targeted: None

wsrep patch for MySQL 5.1 series. This series continues 0.8 series and makes it obsolete

0.8 series Active Development
Latest releases: 0.8.2, 0.8.1, 0.8.0, 0.8pre
Bugs targeted: 1 New, 1 Invalid, 11 Won't Fix, 1 Confirmed, 2 Triaged, 84 Fix Released
Blueprints targeted: None

a series to follow wsrep API 0.8 version: https://launchpad.net/wsrep/+milestone/0.8

0.7 series Current Stable Release
Latest releases: 0.7.6, 0.7.5, 0.7.4, 0.7.3, 0.7.2, 0.7.1
Bugs targeted: 1 Invalid, 3 Won't Fix, 74 Fix Released
Blueprints targeted: 1 Implemented

0.7 bugfix release series

This patch implements hooks inside MySQL/Innodb engine, which can be used to build external replication system for MySQL servers. The replication system built on these hooks can be asynchronous or synchronous and have single or multi-master support.

The replication hooks provide management of transaction write sets:

* populating of write sets, in the sending side
* applying of write sets, in the receiving end

The applying happens by high priority transaction(s). Innodb lock manager has been modified to give preference to dedicated high priority MySQL threads.

There are also calls for providing "total order isolated" processing of certain SQL statements. This feature guarantees that each MySQL server in the cluster process the SQL statement in the same order and uninterrupted. .e.g. all DDL statements need to be processed isolated, to maintain data consistency in the cluster.

Mailing list: http://groups.google.com/group/codership-team?hl=en

0.6 series Obsolete
Blueprints targeted: None

This series contains the work from project start through demo-1, demo-2 up to 0.6 releases. The final 0.6.2 release can be considered of alpha level.

trunk series Active Development
Latest releases: 0.8, 0.7, 0.6.2, 0.6.1, 0.6, demo-2, 0.1alpha, demo-1
Bugs targeted: 10 Invalid, 1 Won't Fix, 1 Confirmed, 14 Fix Committed, 135 Fix Released
Blueprints targeted: 1 Implemented

The "trunk" series represents the primary line of development rather than a stable release branch. This is sometimes also called MAIN or HEAD.

stable series Active Development
Bugs targeted: 1 Invalid
Blueprints targeted: None

stable demo release

18 of 8 results