Add-on & README: Change "Flamenco 3" to just "Flamenco"

When Flamenco 3 was just released, it was important to indicate the
difference between the Flamenco 2 panel (which was just labeled
"Flamenco"), and the new Flamenco 3 panel. The release of v3.0 was
almost two years ago, so it's time to remove the "3" from the titles and
just name things "Flamenco".

CHANGELOG.md

@@ -6,6 +6,7 @@ bugs in actually-released versions.
 
 ## 3.6 - in development
 
+- Change the name of the add-on from "Flamenco 3" to just "Flamenco".
 - Add `label` to job settings, to have full control over how they are presented in Blender's job submission GUI. If a job setting does not define a label, its `key` is used to generate one (like Flamenco 3.5 and older).
 - Add `shellSplit(someString)` function to the job compiler scripts. This splits a string into an array of strings using shell/CLI semantics.
 - Make it possible to script job submissions in Blender, by executing the `bpy.ops.flamenco.submit_job(job_name="jobname")` operator.

README.md

@@ -1,6 +1,6 @@
-# Flamenco 3
+# Flamenco
 
-This repository contains the sources for Flamenco 3. The Manager, Worker, and
+This repository contains the sources for Flamenco. The Manager, Worker, and
 Blender add-on sources are all combined in this one repository.
 
 The documentation is available on https://flamenco.blender.org/, including

addon/README.md

@@ -1,4 +1,4 @@
-# Flamenco 3 Blender add-on
+# Flamenco Blender add-on
 
 ## Setting up development environment
 

addon/flamenco/__init__.py

@@ -3,7 +3,7 @@
 # <pep8 compliant>
 
 bl_info = {
-    "name": "Flamenco 3",
+    "name": "Flamenco",
     "author": "Sybren A. Stüvel",
     "version": (3, 6),
     "blender": (3, 1, 0),

addon/flamenco/gui.py

@@ -22,7 +22,7 @@ class FLAMENCO_PT_job_submission(bpy.types.Panel):
     bl_space_type = "PROPERTIES"
     bl_region_type = "WINDOW"
     bl_context = "output"
-    bl_label = "Flamenco 3"
+    bl_label = "Flamenco"
 
     # A temporary job can be constructed so that dynamic, read-only properties can be evaluated.
     # This is only scoped to a single draw() call.