Let's release a v0.2

[johannesjh]

There have been many improvements during the past few months, thanks to @cbm755 and @real-yfprojects, which means we could release a new version.

• I tagged issues and merge requests with v0.2 in github's issue tracker. This makes it easy to see what has changed since v0.2
• We probably should start writing release notes. Let's determine a simple format, e.g., a Release Notes.rst file that we include into the documentation. It would be nice if these release notes could show up in pypi as well. See adds a changelog #54
• We could (should?) bump dependency versions using poetry update, just to keep things up to date. See updates dependencies #55
• We should test a release candidate, e.g., by using it in our projects
• We can then publish a release by following the documentation, i.e., tagging a commit is all that is needed to publish to pypi

[real-yfprojects]

Should the release notes contain only changes to req2flatpak.py or also changes to the dev setup, ...?

• It would be nice if these release notes could show up in pypi as well

We can add the file to the tools.poetry.readme list.

[real-yfprojects]

This release basically includes a bug fix (#39) and yaml support.

[johannesjh]

Yes, essentially one feature (yaml support) and two bugfixes (#34 and #39).

[johannesjh]

I created an initial draft of the changelog in merge request #54. feedback, corrections, improvements etc are of course welcome!

[johannesjh]

To test the code before its release, I started using the latest version of req2flatpak in favagtk

UPDATE:
favagtk's autoupdate script ran successfully using the new version of req2flatpak.

[johannesjh]

I think we are ready for releasing a v0.2.0, following our own instructions for publishing a release.

I submitted pull request #60 to prepare for the release.

[johannesjh]

done, we published v0.2