-
Notifications
You must be signed in to change notification settings - Fork 286
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
Vibe.d 0.8.3 should be released soon as 0.8.2 doesn't work with master #2058
Comments
Just a friendly ping on this one - 2.079 is coming closer and currently the latest release doesn't compile with dmd-beta |
I updated the change log and tagged beta.1 now. BTW, I had to remove the alpha.5 tag, because the |
oh how awesome real semVer would be |
0.x.y not having any backwards compatibility constraints is SemVer ;) But the point is that currently more or less every release contains a few small breaking changes, so it wouldn't help much to change the versioning scheme. The development mode needs to change as well, and this is what happens with the new individual packages, such as vibe-core. On the other hand, it wouldn't make sense to switch the development mode for "vibe-d" now, because there is still too much known/planned improvements to the old API. It would cause some severe slowdown of development and adoption of new "0.major" releases. For reference: Release candidates vibe.d 0.8.3-rc.1 and vibe-core 1.4.0-rc.1 |
Note: Travis-CI is failing because of this. https://travis-ci.org/veelo/Pascal2D/builds/364566452 |
Hm, this should actually be closed, as 0.8.3 has already been released on 3/8. Can you try to "dub upgrade" to see whether there are still any errors? |
I see. Maybe this means the docker image is outdated? I'll have to figure out how to |
I am not sure that I am following what you are saying. I need a newer dub version? I just tried this locally on Windows, dmd v2.079.0, dub 1.8.0.
My
So there is no direct dependency on vibe-d or ddox in
The strange thing is, that locally it even attempts to use vibe-d 0.8.1 whereas Travis already uses 0.8.2. Should we conclude that dub itself should require vibe-d 0.8.3 when it does a ddox build, but fails to do so? Is that why you suggest to
? |
No you shouldn't need one, but I only briefly looked at your reply and wasn't sure what your CI error was about.
Anyhow looking at ddox, I think the problem is the following
(from: https://github.com/rejectedsoftware/ddox/blob/master/dub.sdl) So dub takes whatever vibe-d is locally available before downloading a new one and 0.8.1 is apparently found in your local dub cache. |
Removing 0.8.1 and 0.8.2 does not help, 0.8.1 is refetched:
Still strange that it wants 0.8.1 locally and 0.8.2 on Travis, but neither is right. |
(I just realised that I removed the wrong version above, but redoing this and leaving only 0.8.3 on the system it still goes and fetches 0.8.1.) |
Oh, I didn't realize that this happens for a |
Locally it can be that an older version of SCOD is still installed and that is used instead of looking for the latest one. |
O thanks a lot @s-ludwig! I was about to post a very long |
No problem! Closing this. |
(I just bumped into this here: dlang-tour/core#662)
At the moment,
dmd-nightly
only works with the alpha0.8.3
release which is scheduled for a beta on 14.2 and to be released at 01.03To avoid any problems, it would be great if vibe.d 0.8.3 could be released in February.
Also it would be better if we could use SemVer for real patches - it was rather annoying to manually bump all packages which require vibe.d.
Here's a quote from a recent discussion at dfmt which explains it better:
Why is this occurring?
See dlang/phobos#5921
tl;dr: it has been decided that making breaking changes to std.experimental.allocator is okay.
The text was updated successfully, but these errors were encountered: