Showing entries 1 to 10 of 87
10 Older Entries »
Displaying posts with tag: gpl (reset)
Releasing ProxySQL 2.0.17

ProxySQL is proud to announce the latest release of ProxySQL version 2.0.17 on the 8th of February 2021

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, or the Docker image available on our Official ProxySQL Docker Repository.  ProxySQL is freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights

ProxySQL v2.0.17 is a patch release comprising of minor backward compatible changes and bug fixes.

Be sure to try out the new ProxySQL 2.0.17 release and …

[Read more]
Releasing ProxySQL 2.0.16

ProxySQL is proud to announce the latest release of ProxySQL version 2.0.16 on the 26th of January 2021

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, or the Docker image available on our Official ProxySQL Docker Repository.  ProxySQL is freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights

ProxySQL v2.0.16 is a patch release comprising of minor backward compatible changes and bug fixes. This release brings several fixes to ProxySQL’s Native Galera monitor, AWS Aurora and connection handling.

[Read more]
Releasing ProxySQL 2.0.15

ProxySQL is proud to announce the latest release of ProxySQL version 2.0.15 on the 30th of October 2020

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights

ProxySQL v2.0.15 is a patch release comprising of minor backward compatible changes and bug fixes.

The most interesting highlight of this release is the introduction of ARMv8 64-bit packages which have been compiled for CentOS-RHEL 7/8, Debian 9/10 and Ubuntu 18/20 as well as a Docker image available on our …

[Read more]
Releasing ProxySQL 2.0.14

ProxySQL is proud to announce the release of the latest stable version of ProxySQL 2.0.14 on the 8th of September 2020

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights

Before discussing the features and fixes in this release we’d like to mention that we are aware of the delays in new releases. Ideally we would like to release ProxySQL more rapidly however we have recently been focusing our development efforts on ProxySQL 2.1.

The next edition of ProxySQL brings improved performance as well as many new and exciting …

[Read more]
Releasing ProxySQL 2.0.13

ProxySQL is proud to announce the release of the latest stable version of ProxySQL 2.0.13 on the 15th of July 2020

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights

New Features

Although only bug fixes are supposed to go into ProxySQL 2.0, we had to introduce a few minor new features:

  • A client can force ProxySQL to run a query in a new connection using a query annotation using create_new_connection=1 in a comment. For example SELECT /* create_new_connection=1 */ 1 . See #2874
  • Added …
[Read more]
Releasing ProxySQL 2.0.12

ProxySQL is proud to announce the fast track release of the latest stable version of ProxySQL 2.0.12 on 18th of May 2020

ProxySQL is a high performance, high availability, protocol aware proxy for MySQL, with a GPL license! It can be downloaded here or alternatively from the ProxySQL Repository, and freely usable and accessible according to the GNU GPL v3.0 license.

Release Overview Highlights Enhancements

  • Added tracking capability for variable group_concat_max_len #2709
  • Do not compile if GIT_VERSION is not set #2768
  • Several new automated …
[Read more]
Some thoughts on recent events

It was suggested by Monty that the posts I've made about MariaDB are for publicity. This simply isn't true. I would have much preferred a different outcome in my interactions with MariaDB. I figured that they would end up giving me a hard time, and I'd be stubborn and we'd both hate each other for as long as I could keep from leaving. A quick separation actually seems much better in such context. Regardless, I would have preferred to speak amicably to the MariaDB Corporation about switching the license back, or at least moving to the new license at the time of the notification of the community, ie as the LAST checkin in the 2.0 branch. I would suggest they re-release 2.0 as GPL and move 2.1 to the BSL to allow the market to decide if they want to move to 2.1, or even take up 2.0, if they aren't guaranteed important (especially security!) fixes in the older …

[Read more]
BSL BS: How do you backport fixes from MaxScale 2.0 to MaxScale 1.0?

I have created a GitHub fork of MaxScale which does not include the 2.0 branch.  The repository is called GPLScale.

There is a big potential problem with this.  Take for example the file server/core/utils.c, which now has a new license:
https://github.com/mariadb-corporation/MaxScale/blob/2.0/server/core/utils.c

This file WAS covered under GPL:
  https://github.com/mariadb-corporation/MaxScale/blob/cb3213af6382c380df9fc47347764f087ae7ecb4/server/core/utils.c

When there is a bugfix in 2.0 for server code that existed in 1.0, can that code be backported directly into GPLscale?

a) util.c in 2.0 is clearly …

[Read more]
BSL BS: How do you backport fixes from MaxScale 2.0 to MaxScale 1.0?

I have created a GitHub fork of MaxScale which does not include the 2.0 branch.  The repository is called GPLScale.

There is a big potential problem with this.  Take for example the file server/core/utils.c, which now has a new license:
https://github.com/mariadb-corporation/MaxScale/blob/2.0/server/core/utils.c

This file WAS covered under GPL:
  https://github.com/mariadb-corporation/MaxScale/blob/cb3213af6382c380df9fc47347764f087ae7ecb4/server/core/utils.c

When there is a bugfix in 2.0 for server code that existed in 1.0, can that code be backported directly into GPLscale?

a) util.c in 2.0 is clearly …

[Read more]
Basically Shitty License

Monty announced that he has created a new non-open source license called the "Business Source License" or BSL.  I think it should have a different name...

You see, Monty has fundamentally crafted a straw man to stand in for the general Open Source model by applying his experience in the dog-eat-dog world of forked software, in particular, the "ecosystem" of MySQL.  The software that MariaDB draws the majority of their income from is MariaDB, which is a fork of MySQL.  If you don't know the history, well, you see, SUN bought MySQL, Oracle bought Sun, and Monty, in an environment of nearly Biblical levels of FUD, forked MySQL into MariaDB (both products are named after his daughters).

While MariaDB was originally envisioned as a "drop in/drop out" replacement, it has diverged so far from the Oracle product that it is no longer even "drop in" with the latest versions of MySQL. Oracle is adding amazing new …

[Read more]
Showing entries 1 to 10 of 87
10 Older Entries »