Bump version numbers in the dev branch ahead of master to avoid confusion.

doc/en/Developer/Releasing.md

@@ -23,7 +23,7 @@ Check
 * Check version numbers on stackmaxima.mac.
 * Run unit tests.
 * Run code checker.
-* Commit all changes to git, e.g. "Update version number for the 4.3.6 release."
+* Commit all changes to git, e.g. "Update version number for the 4.3.11 release."
 
 ## 2. Create new tag with version name
 
@@ -32,7 +32,7 @@ E.g. "v4.3.6".
 * Push to GitHub.
 * Push tags to GitHub 
  * Tortoise git: pulldown from push
- * Linux: `git tag -a v4.3.6 -m "Update version number for the 4.3.6 release."`
+ * Linux: `git tag -a v4.3.11 -m "Update version number for the 4.3.11 release."`
  * Linux: `git push`
  * Linux: `git push --tags`
 

stack/maxima/stackmaxima.mac

@@ -3105,5 +3105,5 @@ load(linearalgebra);
 
 /* Stack expects some output with the version number the output happens at */
 /* maximalocal.mac after additional library loading */
-stackmaximaversion:2021120900$
+stackmaximaversion:2021130900$
 

version.php

@@ -24,12 +24,12 @@
 
 defined('MOODLE_INTERNAL') || die();
 
-$plugin->version   = 2021120900;
+$plugin->version   = 2021130900;
 $plugin->requires  = 2018051700;
 $plugin->cron      = 0;
 $plugin->component = 'qtype_stack';
-$plugin->maturity  = MATURITY_STABLE;
-$plugin->release   = '4.3.10 for Moodle 3.9+';
+$plugin->maturity  = MATURITY_ALPHA;
+$plugin->release   = '4.3.11 for Moodle 3.9+';
 
 $plugin->dependencies = array(
     'qbehaviour_adaptivemultipart'     => 2020103000,