search

jvilk / BrowserFS

BrowserFS is an in-browser filesystem that emulates the Node JS filesystem API and supports storing and retrieving files from various backends.
Other
3.06k stars 216 forks source link

Create a new release #362

Closed AntonOfTheWoods closed 10 months ago

AntonOfTheWoods commented 11 months ago

The build system currently has some issues and it requires quite a lot of effort to understand what is going on. Many years appear to have passed since a new version has been released, and many features and bugs are missing in the npm version. Could a beta2 be released to ease these pain points?

james-pre commented 11 months ago

I'm working on getting NPM publish permissions from jvilk but he is very busy IRL so that is taking a while.

You currently have to build from the latest commit.

AntonOfTheWoods commented 10 months ago

@james-pre you closed this because it was annoying you rather than because a release was made?

james-pre commented 10 months ago

@AntonOfTheWoods No. I closed this because while I would love to create a new release, I don't have the permissions. The purpose of issues (in my opinion) are to bring up questions and concerns of any kind that should be addressed. I guarantee the second I have permissions, a new beta will be released (provided CI checks are successful). Hence, there is not a reason for the issue to remain open.

AntonOfTheWoods commented 10 months ago

Sure. I agree there are lots of project maintainers who have that view of issues, and the maintainer makes the rules. Personally, I prefer the view that issues function as points of contact for active issues that users/Devs encounter with the codebase. Until the issue is resolved, a ticket stays open so others don't create new issues needlessly, and can quickly see what is ongoing (and they might lend a hand...). A wontfix is definitely also a resolution, of course! But plenty of maintainers don't agree with me, so I'll not bother you further!

james-pre commented 10 months ago

@AntonOfTheWoods I 100% agree with you. Feel free to re-open the issue if you want. I'm doing everything I can to get a release out but @jvilk is very busy and I need him to give me permissions on NPM.