[RFE] Making a new release

[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 😊

[f-f]

Will release once #1298 is merged

[Hi-Angel]

Thanks! I subscribed to the PR

[Hi-Angel]

@f-f hello, it's been two weeks since you merged the PR, any news? 😊

[f-f]

We are almost good to release in general availability, the last blocker left is the block of work in purescript/registry-dev#696 and purescript/registry-dev#669, which will require re-uploading the Registry. We can't mark the new Spago as ready to use until things are properly stable.

[Hi-Angel]

I see. Should perhaps the issue be re-opened? I see that purescript/registry-dev#696 has been open for ½ an year with no comments/discussions/PRs, so it may easily hang there for months or years.

[f-f]

I don't see the point in tracking this in yet another place where it's not particularly actionable, keep an eye on those tickets if you'd like to be updated on the progress

[Hi-Angel]

I don't see the point in tracking this in yet another place

Oh, sorry, did I miss, is it tracked somewhere already?

where it's not particularly actionable

Is "making a release" not an action?

keep an eye on those tickets if you'd like to be updated on the progress

The problem is the tickets in a completely unrelated project, and if someone will comment another ½ an year later in purescript/registry-dev#696 I won't even figure out why I am subscribed to the issue in the first place.

[f-f]

Oh, sorry, did I miss, is it tracked somewhere already?

Yes, the tickets I linked above

Is "making a release" not an action?

We likely won't need another release, as I explained above we need changes in the registry before announcement

The problem is the tickets in a completely unrelated project

It's a very related project.