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

Switches default boilerplate from ir-boilerplate-2016 to ir-boilerplate #1057

Merged
merged 2 commits into from
May 25, 2017

Conversation

jamonholmgren
Copy link
Member

Moving from the venerable ignite-ir-boilerplate-2016 to the fresh, hot ignite-ir-boilerplate version 2.0.0 (Andross), which is currently released as 2.0.0-rc.1.

@jamonholmgren jamonholmgren added this to the 2.0.0-beta.10 milestone May 25, 2017
@jamonholmgren jamonholmgren self-assigned this May 25, 2017
@jamonholmgren jamonholmgren requested review from skellock and GantMan May 25, 2017 06:50
@jamonholmgren
Copy link
Member Author

Once #1056 is merged and subsequently this one, let's release ignite-cli@2.0.0-rc.1 here (@skellock, can you handle that tomorrow?). Then we're ready to test the two release candidates for a week or so and then release 2.0.0 next week. Ref #1047.

@jamonholmgren jamonholmgren mentioned this pull request May 25, 2017
21 tasks
Copy link
Contributor

@skellock skellock left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we renaming the repo from ignite-ir-next to ignite-ir-boilerplate? Pick an option:

  • Yes
  • Yes

@skellock
Copy link
Contributor

I can release this yes. I would prefer to show someone how though.

@jamonholmgren
Copy link
Member Author

Updated to ignite-ir-boilerplate.

@skellock skellock merged commit b5c80a1 into master May 25, 2017
@skellock skellock deleted the point-to-andross branch May 25, 2017 18:48
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