Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-3164

Add MySQL 5.6 to test matrix

XMLWordPrintable

    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      MySQL 5.6.10 represents the first GA release of 5.6. However, it cannot be used with Stash due to a serious issue with its query optimizer.

      This issue has 2 deliverables:

      • Monitor the MySQL bug for a fix version and validate it
      • Deploy an image with the fixed version to the build farm and add it to the DAO matrix tests to validate 5.6 support going forward

      Until a version including a fix for that issue is specified, 5.6 cannot be used by Stash, and will not be supported if deployed at customer sites. Stash 2.2 includes changes, made under STASH-3133, which will block attempts to start Stash when connected to MySQL 5.6, as well as to block attempts to migrate from HSQL to MySQL 5.6 or setup MySQL 5.6 as the external database.

      Customers interested in using MySQL 5.6 with Stash may track this issue for status, as well as the referenced MySQL bug.

      Note: This bug also precludes the use of Amazon Aurora, which as of 2017-03-31 is based on MySQL 5.6.10a

            [BSERV-3164] Add MySQL 5.6 to test matrix

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3397418 ] New: JAC Suggestion Workflow 3 [ 3616041 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: BSERV Suggestions Workflow [ 3391753 ] New: JAC Suggestion Workflow [ 3397418 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Stash Workflow - Restricted [ 1447367 ] New: BSERV Suggestions Workflow [ 3391753 ]
            Issue Type Original: Development Task [ 12 ] New: Suggestion [ 10000 ]
            Priority Original: Low [ 4 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Dave Chevell made changes -
            Description Original: MySQL 5.6.10 represents the first GA release of 5.6. However, it cannot be used with Stash due to a [serious issue|http://bugs.mysql.com/bug.php?id=68424] with its query optimizer.

            This issue has 2 deliverables:
            - Monitor the MySQL bug for a fix version and validate it
            - Deploy an image with the fixed version to the build farm and add it to the DAO matrix tests to validate 5.6 support going forward

            Until a version including a fix for that issue is specified, 5.6 cannot be used by Stash, and will not be supported if deployed at customer sites. Stash 2.2 includes changes, made under STASH-3133, which will block attempts to start Stash when connected to MySQL 5.6, as well as to block attempts to migrate from HSQL to MySQL 5.6 or setup MySQL 5.6 as the external database.

            Customers interested in using MySQL 5.6 with Stash may track this issue for status, as well as the referenced MySQL bug.

            Note: This bug also precludes the use of Amazon Aurora, which as of 2017-03-31 is based on MySQL 5.6.10             		New: MySQL 5.6.10 represents the first GA release of 5.6. However, it cannot be used with Stash due to a [serious issue|http://bugs.mysql.com/bug.php?id=68424] with its query optimizer.

            This issue has 2 deliverables:
            - Monitor the MySQL bug for a fix version and validate it
            - Deploy an image with the fixed version to the build farm and add it to the DAO matrix tests to validate 5.6 support going forward

            Until a version including a fix for that issue is specified, 5.6 cannot be used by Stash, and will not be supported if deployed at customer sites. Stash 2.2 includes changes, made under STASH-3133, which will block attempts to start Stash when connected to MySQL 5.6, as well as to block attempts to migrate from HSQL to MySQL 5.6 or setup MySQL 5.6 as the external database.

            Customers interested in using MySQL 5.6 with Stash may track this issue for status, as well as the referenced MySQL bug.

            Note: This bug also precludes the use of Amazon Aurora, which as of 2017-03-31 is based on MySQL 5.6.10a
            Dave Chevell made changes -
            Description Original: MySQL 5.6.10 represents the first GA release of 5.6. However, it cannot be used with Stash due to a [serious issue|http://bugs.mysql.com/bug.php?id=68424] with its query optimizer.

            This issue has 2 deliverables:
            - Monitor the MySQL bug for a fix version and validate it
            - Deploy an image with the fixed version to the build farm and add it to the DAO matrix tests to validate 5.6 support going forward

            Until a version including a fix for that issue is specified, 5.6 cannot be used by Stash, and will not be supported if deployed at customer sites. Stash 2.2 includes changes, made under STASH-3133, which will block attempts to start Stash when connected to MySQL 5.6, as well as to block attempts to migrate from HSQL to MySQL 5.6 or setup MySQL 5.6 as the external database.

            Customers interested in using MySQL 5.6 with Stash may track this issue for status, as well as the referenced MySQL bug.             		New: MySQL 5.6.10 represents the first GA release of 5.6. However, it cannot be used with Stash due to a [serious issue|http://bugs.mysql.com/bug.php?id=68424] with its query optimizer.

            This issue has 2 deliverables:
            - Monitor the MySQL bug for a fix version and validate it
            - Deploy an image with the fixed version to the build farm and add it to the DAO matrix tests to validate 5.6 support going forward

            Until a version including a fix for that issue is specified, 5.6 cannot be used by Stash, and will not be supported if deployed at customer sites. Stash 2.2 includes changes, made under STASH-3133, which will block attempts to start Stash when connected to MySQL 5.6, as well as to block attempts to migrate from HSQL to MySQL 5.6 or setup MySQL 5.6 as the external database.

            Customers interested in using MySQL 5.6 with Stash may track this issue for status, as well as the referenced MySQL bug.

            Note: This bug also precludes the use of Amazon Aurora, which as of 2017-03-31 is based on MySQL 5.6.10

            Bryan Turner (Inactive) added a comment -

            Ross,

            Take a look at BSERV-8145. I wrote that 5.7 would remain unsupported in February of 2014. It remained unsupported at that time because the only releases available then were prereleases, not GA. After 5.7 went GA, it was added to backlog for support, which ships in 4.10.

            Best regards,
            Bryan Turner
            Atlassian Bitbucket

            Bryan Turner (Inactive) added a comment - Ross, Take a look at BSERV-8145 . I wrote that 5.7 would remain unsupported in February of 2014. It remained unsupported at that time because the only releases available then were prereleases, not GA. After 5.7 went GA, it was added to backlog for support, which ships in 4.10. Best regards, Bryan Turner Atlassian Bitbucket

            Ross Golder added a comment -

            I'm looking for more information on why 5.7 will remain unsupported. The comments above do not make this clear.

            Ross Golder added a comment - I'm looking for more information on why 5.7 will remain unsupported. The comments above do not make this clear.
            Owen made changes -
            Workflow Original: Stash Workflow [ 496001 ] New: Stash Workflow - Restricted [ 1447367 ]
            M (Inactive) made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 56460 ] New: This issue links to "Page (Extranet)" [ 56460 ]
            steve made changes -
            Remote Link Original: This issue links to "Page (Extranet)" [ 56460 ] New: This issue links to "Page (Extranet)" [ 56460 ]

              bturner Bryan Turner (Inactive)
              bturner Bryan Turner (Inactive)
              Votes:
              16 Vote for this issue
              Watchers:
              45 Start watching this issue

                Created:
                Updated:
                Resolved: