[MDEV-22412] 2020 Q2 release merge Created: 2020-04-29  Updated: 2020-07-14  Resolved: 2020-05-09

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Fix Version/s: 5.5.68, 10.1.45, 10.2.32, 10.3.23, 10.4.13, 10.5.3

Type: Task Priority: Blocker
Reporter: Sergei Golubchik Assignee: Oleksandr Byelkin
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
PartOf
includes MDEV-22394 Merge new release of InnoDB 5.7.30 to... Closed

 Description   
  • 5.5
    • mysql-5.6
  • 10.1
    • 5.5
    • InnoDB-5.6
    • XtraDB-5.6
    • perfschema-5.6 (mysql) (no changes)
    • TokuDB-5.6 (percona)
    • Connect 10.1
    • Mroonga (no changes)
    • PCRE
  • 10.2
    • 10.1
    • InnoDB-5.7
    • Connect 10.2 (bring no changes)
    • C/C v3.1
      • see if 5.5/10.1 changes in client.c should be applied to C/C
      • ask Georg if everything is pushed for a release
      • make sure e8e67bd4a4c is in C/C
  • 10.3
    • 10.2
    • oracle mode parser
  • 10.4
    • 10.3
    • wolfssl 4.4.0
  • 10.5
    • perfschema-5.7 (mysql) (no changes)
    • change maturity to gamma


 Comments   
Comment by Marko Mäkelä [ 2020-07-14 ]

We missed the XtraDB 5.6.48-88.0 release. There were no other applicable changes than the version number change, because the MySQL 5.6.48 changes had already been applied to both InnoDB and XtraDB.

Generated at Thu Feb 08 09:14:33 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.