Making a release 0.1

[kjvbrt]

Hi :)

Since #43 and #48 are interconnected, and #43 needs some more work which will be done later, I would like to have a release. I suggest to have release 0.1 and have it permanently deployed.

[brauliorivas]

Nice. So, would you like to have the release now? or wait for #43 and #48 to be merged and then have a release? If the second is the case, we could wait for both PR's to be merged into main and push to release branch the changes. We would only need to create a new branch from main, called release and it will be automatically deployed (I can do it). If not, then I will create the branch before that gets merged (and add somewhere some v0.10 label into that deploy, maybe on the info modal).

[brauliorivas]

Release deployed!

https://key4hep.github.io/eede/release/

[tmadlener]

Done and deployed