First of all, MyDumper is v0.A.B-C , that ZERO (0) at the begining means that we still developing MyDumper, as I usually say, MyDumper can be used for production but it is not production ready. The goal that I set every year is to release v1 which is going to be the first stable release and production ready. When is going to happen? I'm not going to answer now, but check below!

So, during v0, A means major version, B means minor and C is patching.

If I found a backward compatibility at file level, then I increase A. This means that file manipulation will not the same on different major versions. It doesn't means that it will never work, there might be scenarios where it could work, but I'm not documenting them as the amount of possibilities might be huge.

We try to fill a bucket as much as possible with features and bug fixes, and after a couple of months or when we found bugs that can't be patch to current version, we release a new version.

As soon as we release a major or minor version, users start to detect bugs. Mostly are easy fixes that we can patch and release a patching version. Usually patching version are releases during the first 2 weeks after a major/minor release.

We have been working to understand all the use cases that we have. However, there are new use cases all the time and it has been challenging to change mydumper and myloader to work as one single tool. What I can say right now, if we don't change or find something that we need to change in the main engine of mydumper and myloader for at least 6 months, then we are going to be able to release a v1. Honestly, I hope to start 2024 with a stable production ready version, as last changes that we did on mydumper and myloader opened the engines and reduced the memory usage which was a huge issue before.