Drop experimental flag and release 0.6.0

[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.

[kannes]

Sorry for the huuuuuge delay... 😢

I'll do it on Monday

[kannes]

@Guts @jmkerloch I feel no need to rush it now and since you guys are currently active, let's plan it a bit. How does this look to you? My goal would be to release it this week :)

Merges we should include

At least in my opinion, shout if you disagree

• experimental=False Drop experimental flag #55
• Documentation: Documentation: complete contributing guide and publish to GitHub Pages using GitHub Actions #52
• supportsQt6=True Check Qt6 support flag #57

Feel welcome to merge those or tell me to do it once ready.

Other current issues

• The docstring/example fix can come later in my opinion: Use verbatim text in config file examples #56

Release

• changelog.md
• tag 0.7.0

After the release

• @kannes Release final old version #48

[Guts]

Working on translation in #54 I realized that refactoring have broken a lot of translated strings. From my point of view, it's not a blocking task for the stable release but it should be in the following steps.

[kannes]

Yay, that worked!

https://github.com/WhereGroup/profile_manager/releases/tag/0.6.0 and https://plugins.qgis.org/plugins/profile_manager/version/0.6.0/ were automatically created.

The changelog update in the metadata.txt file did not work but I guess it is my fault, because I had manually added something in the repo. I'll remove that (edit: done)and we will see what happens on the next release. It's not that important to me. If it is worthy a new release for you, just shout.

[Guts]

Hurray! Congrats @kannes, welcome to qgis-plugin-ci users 🤗! (cc @Gustry @3nids)
As we say by here: APÉRO 🍻 or 🍵 !

The changelog update in the metadata.txt file did not work but I guess it is my fault, because I had manually added something in the repo. I'll remove that (edit: #61 we will see what happens on the next release. It's not that important to me. If it is worthy a new release for you, just shout.

It's not your fault. I forgot to specify that qgis-plugin-ci does not handle headers. So in the changelog, you've to write a "flat" markdown. I fixed it quickly with ccc6ec8.

[Gustry]

Nice @kannes !

Yes, I forgot about this old ticket about supporting sub-sections in a changelog : opengisch/qgis-plugin-ci#56 :)

[Guts]

@kannes do you have a Mastodon account? I would like to broadcast this achievement on this social network and credit you for all the good work you do on this plugin?

[kannes]

@kannes do you have a Mastodon account? I would like to broadcast this achievement on this social network and credit you for all the good work you do on this plugin?

One step ahead of you :D https://norden.social/@cartocalypse/114274411395953864