KScript release process about kscript

[aartiPl]

Ok. Then I will work on migration to the new organization in the next iteration. (I have just created kotlin-scripting organization; you are invited)

In the meantime can you please review the NEWS file? I have added there all the features I would like to release in kscript 4.1. I would appreciate it if you can comment on them.

To fully support updated annotations @CompilerOptions and @KotlinOptions there is a need to update kscript-annotations repository.

Do you think you can help with releasing a new version of kscript-annotations (should happen before the release of a new version of kscript) and then the release of a new version of kscript itself?

[holgerbrandl]

Sure thing. Great idea, first step would be to move the repo-namespace I think. Unfortunately I don't have much time in the coming months to support this process. So maybe a hard break (with transition process) is also an option to to make sure all you hard work will reach the users.

[aartiPl]

I now have .kts script for doing releases and most of the credentials available. The script still needs to be put in the kscript repository as it depends on the not yet published library.

The changes include:

• new docker hub repository: https://hub.docker.com/r/kscripting/kscript/tags
• new homebrew repository: https://github.com/kscripting/homebrew-tap

The last part that needs to be added is the releases to ArchLinux repository. I have created my ArchLinux user (aartiPl), but now I need to become co-maintainer of the kscript repository:

https://aur.archlinux.org/packages/kscript

@holgerbrandl, @ others - do you know how to become co-maintainer of kscript? Any hints on how to do that correctly/quickly?

[aartiPl]

I have access to all release channels. I am closing this ticket as done.