Drop experimental flag

[kannes]

I would feel OK with dropping the experimental flag now. The big refactor is in and I added some nice UI/UX improvements after feedback from a colleague. There are still many things to do, and the quality of the actual data discovery and transfer is questionable, but let's do it!

I propose we set experimental=False and release a new version.

What do you think @Guts?

I did not really use care and already set the version up to 0.6.0 after merging my big refactor. Should we use that with the few extra improvements added in the meantime or should we go to 0.7.0? The 1.0.0 would be more appropriate for when there is a decent testsuite in my opinion, but I would not fight against a 1.0.0 either.

The release process would be:

• Update changelog in metadata.txt
• Set appropriate version in metadata.txt
• Set experimental=False in metadata.txt
• Commit and make a tag for the version
  • This automatically packages and uploads the new version to plugins.qgis.org

Right? The CHANGELOG.md is then automatically updated as I understand it?

[Guts]

I agree, it's time for this plugin to face the stable channel!

About the release workflow it's the reverse: switch the experimental flag, bump the version, fill the changelog.md with the version number and listing changes. Then apply the git tag with the exact same version number you want to release and push it to the default branch.
Let the magic happens 🧙‍♂️. The metadata.txt sections are automatically filled from the git tag and changelog.md. Note that the experimental flag is also automatically set depending on the version suffixes, complying with semver (0.7.0-beta1 - - > experimental=true ; 0.7.0 - - > experimental=false).

I've recently worked on another plugin adding a similar tooling and documented it: https://aeag.github.io/MenuFromProject-Qgis-Plugin/development/packaging.html#release-a-version

Let me know if you need some help.