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

Release process clarification #131

Closed
walterdolce opened this issue Mar 22, 2019 · 5 comments
Closed

Release process clarification #131

walterdolce opened this issue Mar 22, 2019 · 5 comments
Assignees

Comments

@walterdolce
Copy link
Contributor

Hi all. What's the release process adopted in this project?

I was pulling v0.9.0 and expecting my recent changes to be there (i.e. #109) but they are not there 🤔

@walterdolce
Copy link
Contributor Author

To clarify the question above, I am aware of there is some information about release cycles, but that does not explicitly say anything about the PRs that get merged and when they will be released (if ever).

Thanks!

@skpaterson
Copy link

Hi @walterdolce fair point, this has been mostly a manual process up to now but improving that is on the to-do list.

@walterdolce
Copy link
Contributor Author

Glad to hear @skpaterson! Happy to help if needed.

slevenick added a commit to slevenick/inspec-gcp that referenced this issue Apr 3, 2019
@skpaterson skpaterson self-assigned this Aug 23, 2019
@skpaterson
Copy link

Happy to say we've moved to a working automated release setup since #168 so each merged PR will now minimally bump the patch version and create a release tag.

@walterdolce
Copy link
Contributor Author

Excellent work! Thanks!

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

2 participants