Skip to content

KScript release process #376

Description

@aartiPl

Maybe we can create a GitHub organization named: kotlin-scripting and transfer kscript to that organization? Then we could build a release process around a new organization (user names/passwords).

I have also an idea for yet another project - Kotlin wrapper around bash commands. It will allow to finally get rid of bash from user space. At least I hope for that ;-)

'kotlin-scripting' organization could be hosting place for that project also.

Please comment with your suggestions/ideas.

Activity

  1. holgerbrandl commented on Jul 31, 2022

    @holgerbrandl
    Collaborator

    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.

  2. aartiPl commented on Aug 18, 2022

    @aartiPl
    CollaboratorAuthor

    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?

  3. aartiPl commented on Jan 6, 2023

    @aartiPl
    CollaboratorAuthor

    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:

    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?

  4. aartiPl commented on Jan 16, 2023

    @aartiPl
    CollaboratorAuthor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions