-
Notifications
You must be signed in to change notification settings - Fork 511
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
Preparing next release #699
Comments
Dang, yeah, that's 2 years worth of PRs, should probably do it at 2.5 if there's no source breaking changes |
Thanks @orta, happy to go with 2.5 👍 The only potential breaking change could be the one we are about to introduce to fix #698. But we should be able check if |
any update on #698 |
What is the plan for getting Xcode 9 support? Is this something that is going to be done? |
Yes @scottdensmore. I will have a look at the work done by @SevInf and hopefully will try to get the new build out before the end of the year |
Thanks @ecaselles. Anything we can do to help? |
@scottdensmore I am currently reviewing the two PRs opened by @SevInf and hoping to get a green build on #702. Not sure about #701, looks like if we can't keep backwards compatibility, it is just not a minor version bump. |
FYI I will be tagging this release as 3.0, as it will introduce breaking changes (#701) |
I would like to push a new release of Kiwi out to include what it is currently on master, plus the fixes needed to ensure compatibility with Xcode 9 (which we are currently working on).
Initially, the work included in this milestone would be:
any
Macro Conflicts with Generated Swift Header MacroSWIFT_MODULE_NAMESPACE_PUSH
#698: renaming theany
macroI know there were conversations for the next release to be v3.0, but it feels like a minor version bump could be more appropriate, since most of the changes added are bug fixes, memory management improvements and other maintenance work.
@kiwi-bdd/core-team would you be happy for me to tag this release as v2.4.1 or would you rather continue with the plan of naming it v3.0 just for closure?
The text was updated successfully, but these errors were encountered: