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

Packaging Guidance #33

Open
stevendanna opened this issue Jan 21, 2017 · 4 comments
Open

Packaging Guidance #33

stevendanna opened this issue Jan 21, 2017 · 4 comments

Comments

@stevendanna
Copy link

Thanks for making the server-side components open source! I would like to package this up as a habitat package, but noticed that the last tagged version is pretty far behind master. Would you recommend packaging the 1.8 tag or building from master? If master, would it be possible to tag a new release sometime soon that I could point at?

I totally understand if you have reasons for not wanting to tag a release, thanks again for your work on this project!

@nviennot
Copy link
Member

Use master. I'm not sure why I haven't tagged releases on the server side

Thank you :)

@anarcat
Copy link

anarcat commented May 10, 2019

would sure be nice to see tagged releases here as well. :)

@TBK
Copy link

TBK commented May 21, 2019

Please make a new release so distros that does not allow git master builds can get the changes made from 2013 to now.

@LouisKottmann
Copy link

Is the current master branch "release-ready"? Without tags I don't know the current state of the project

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

5 participants