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

Add release #58

Closed
FFY00 opened this issue Mar 27, 2020 · 5 comments
Closed

Add release #58

FFY00 opened this issue Mar 27, 2020 · 5 comments

Comments

@FFY00
Copy link

FFY00 commented Mar 27, 2020

Hey, would it be possible to tag a release so that migen-boards can be properly distributed?

@FFY00
Copy link
Author

FFY00 commented Mar 27, 2020

It would also be great to have releases for the other components, let me know if you want me to open issues there.

@whitequark
Copy link
Member

whitequark commented Mar 28, 2020

The plan for nmigen-boards is that each commit to master would automatically push a tag and a PyPI release, since there is no such thing as "stable boards". Either you track master (for daily work and on CI), or you pin a specific commit / version (for reproducible builds).

This isn't currently implemented, and until it's implemented I don't have any plans to push individual releases manually. Feel free to package HEAD.

@FFY00
Copy link
Author

FFY00 commented Mar 28, 2020

This isn't currently implemented, and until it's implemented I don't have any plans to push individual releases manually. Feel free to package HEAD.

ACK

Would it make sense to sync up with nmigen releases? This only makes sense if there is a possibility for the API to break.

The other components (stdio and soc) are a bit different, what do you want to do there?

@whitequark
Copy link
Member

Would it make sense to sync up with nmigen releases? This only makes sense if there is a possibility for the API to break.

At any given moment, nmigen-boards is supposed to depend on the range of nmigen versions it's guaranteed to be compatible with. (Sometimes that might not be true--it's not easy to get pip to perform minimal version resolution--but that's the intent.)

The other components (stdio and soc) are a bit different, what do you want to do there?

At the moment those components are quite immature and it's too early to talk about releasing them. Let's discuss it once it actually makes sense.

@FFY00
Copy link
Author

FFY00 commented Mar 28, 2020

At the moment those components are quite immature and it's too early to talk about releasing them. Let's discuss it once it actually makes sense.

Sure, please ping me if you remember.

@FFY00 FFY00 closed this as completed Mar 28, 2020
rroohhh pushed a commit to rroohhh/nmigen-boards that referenced this issue Aug 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants