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/0.2.1 #55

Merged
merged 4 commits into from
May 17, 2016
Merged

Release/0.2.1 #55

merged 4 commits into from
May 17, 2016

Conversation

jbeemster
Copy link
Member

Hey @alexanderdean so I have made the changes to the script. There are no changes to the UI or to the actual AMI itself so do I need to build new ones to match the repo version? Or is it okay to leave the published AMI as 0.2.0?

@alexanderdean
Copy link
Member

Hey Josh,

As long as it's 100% unambiguous in all docs that the AMIs continue to be
0.2.0, no need to rebuild the same assets with a new version...
On 17 May 2016 3:17 p.m., "Josh" notifications@github.com wrote:

Hey @alexanderdean https://github.com/alexanderdean so I have made the
changes to the script. There are no changes to the UI or to the actual AMI
itself so do I need to build new ones to match the repo version? Or is it

okay to leave the published AMI as 0.2.0?

You can view, comment on, or merge this pull request online at:

#55
Commit Summary

File Changes

Patch Links:


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#55

@jbeemster
Copy link
Member Author

It is it is. I will merge this across then!

@jbeemster jbeemster merged commit c05503f into master May 17, 2016
@jbeemster jbeemster deleted the release/0.2.1 branch March 20, 2017 09:33
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

Successfully merging this pull request may close these issues.

2 participants