Skip to content

[RFE] Making a new release #1306

Closed
Closed
@Hi-Angel

Description

@Hi-Angel

As been discussed elsewhere, new Spago developments are largely unknown to users, because both releases page as well as the NPM page are still stuck at release from before the fork has been made. This makes a sad irony where formally people are using the new rewritten Spago without knowing it's technically still the older one.

Additionally, there's a category of users who can't rely on unreleased software. For example, I personally would prefer not to do that, because ATM I'm the only person working on the project, and when new people will get hired, I'd prefer for them to have the least problems possible, so I'd prefer not to not rely on unreleased Spago, at least not till the team would be bigger.

So all in all, new release is necessary. As it turns out the new release haven't been made not because the project is deemed unstable, but… I'm not sure, I presume it was just forgotten about.

So, please, make a release with the shiny new rewritten Spago so people can use it 😊

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