Adopt Semver-compatible version branches about h5p-php-library HOT 3 OPEN

I agree with you that we should do this, or at least something like this. The question is when I think.

Each branch we commit to maintain has a cost, and with only three developers in the H5P Core team we have to keep the costs low. We're getting more people on board and hopefully we will be able to take on something like this pretty soon.

from h5p-php-library.

Yes, that's why I think it might be best to forget separate branches for each minor release and have just a branch for each major version. That way the maintenance burden is not that bad.

Also git merge command helps. Thanks to it you don't have to commit same fixes manually to all branches, but just merge them up from the lower branches.

from h5p-php-library.

I know, but right now we only have one version of the H5P PHP library for instance. There are branches for the different states of it, but we only release one version of it. That will probably change in the future however.

from h5p-php-library.