Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a release? #217

Open
FFY00 opened this issue May 25, 2019 · 4 comments
Open

Create a release? #217

FFY00 opened this issue May 25, 2019 · 4 comments

Comments

@FFY00
Copy link

FFY00 commented May 25, 2019

Could you please consider creating a release so that this software is suitable for distribution?

@FFY00
Copy link
Author

FFY00 commented Mar 28, 2020

Friendly ping @cliffordwolf

@FFY00
Copy link
Author

FFY00 commented Jun 26, 2020

Sorry to bother, any news on this? I want to package icestorm for Arch Linux.

@romavis
Copy link

romavis commented Sep 16, 2022

This would require icestorm maintainers to have some sort of release schedule, like it's currently done for yosys and nextpnr. That's convenient for end users, but will it bring any actual improvement?

I'm not a maintainer here, so it's just my own impression, but anyway:

  1. Icestorm doesn't seem to undergo many changes these days, so perhaps each new commit on master can be considered a new "release"?
  2. There won't be much difference from using latest master compared to using hand-made release tag. From what I see there's no test suite of any kind, so it's not realistically possible to validate all the code and say "good to be released". Even if there are release tags, they would offer same level of stability as any commit you take from master.
  3. Not having releases doesn't make it impossible for distro maintainters to package icestorm - they can tag package with timestamp instead of a version. One example where this is done is salfter overlay for Gentoo: link. Distros can release packages at their own schedule (at today's pace it's not impossible to have new package revision for every new commit on master branch).

One benefit of adding releases is that versioning scheme can be used to indicate loss of backward compatibility in the interface/API. Does icestorm have any interface important for end users besides CLI options?

Related issues:
#163 #280

@dseight
Copy link

dseight commented Jun 25, 2023

For example, absence of a tagged releases makes it impossible to add icestorm to the macOS homebrew repo (https://docs.brew.sh/Formula-Cookbook#basic-instructions):

Before submitting a new formula make sure your package:
...

  • has a stable, tagged version (i.e. isn’t just a GitHub repository with no versions)

So, for now it's just impossible to make this tools easily accessible for the macOS users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants