python lib changelog adr proposal

[vivus-ignis]

What this PR does / why we need it:

We need to improve the python GL library's release process.

NOTE: adr-dir file added to make it easier for new developers to work with adr-tools as we use non-standard (from the PoV of adr-tools) ADR directory path.

Which issue(s) this PR fixes:
Fixes gardenlinux/python-gardenlinux-lib#229

[yeoldegrove]

I summed up my perspective here: gardenlinux/python-gardenlinux-lib#229

[fwilhe]

To be honest I don't think that this is a problem that needs solving. I'm very eager to get good release notes on user-visible artefacts like Garden Linux releases, but this library is an internal technical artefact. I would appreciate if we focus on issues like the fact that the tests currently fail on the main branch of the lib, or to standardise/automate the release process and/or a debugging setup for github workflows that involve code from the lib.

[vivus-ignis]

To be honest I don't think that this is a problem that needs solving. I'm very eager to get good release notes on user-visible artefacts like Garden Linux releases, but this library is an internal technical artefact. I would appreciate if we focus on issues like the fact that the tests currently fail on the main branch of the lib, or to standardise/automate the release process and/or a debugging setup for github workflows that involve code from the lib.

Changelog process is an obvious first step to make work on this repository more transparent and therefore more disciplined, which imo will also help with the issue of broken tests in the main branch.

The problem is not the lack of automation, but behavior. If the team needs to keep track of a changelog and take care of the release process, there are less chances that untested code gets merged into the mainline.

It's not about the markdown document, it's about the process. And my point of not making this process automatic was exactly because it's about behavior change.

[yeoldegrove]

We currently have at least 3 places where we started discussing this topic ...

• python lib changelog adr proposal #3800
• Create CHANGELOG file python-gardenlinux-lib#229
• initial changelog python-gardenlinux-lib#230

We should finally align, decide, implement something.

[vivus-ignis]

I would add this PR here: gardenlinux/python-gardenlinux-lib#256
This PR proposes to start installing python library as a wheel package (and not from a source git commit).
This change would kickstart the release process and the changelog generation can be done by using github UI itself (it gives an option to generate release notes).

[yeoldegrove]

I would like to close this ADR proposal and implement a solution in e.g. gardenlinux/python-gardenlinux-lib#271.

We're all on the same page that we need to streamline the release process (includes adding a changelog). Let's start defining and implementing the technical process and (if still needed) talk about a changelog format later.