The first release of the revamped core module [1] is nearing, and along with that, a compatible vibe.d release (0.8.0). The new core module is still opt-in in this release and can be activated using a `subConfiguration "vibe-d:core" "vibe-core"` directive in dub.sdl (`"subConfigurations": {"vibe-d:core": "vibe-core"}` in dub.json).

In parallel to the 0.8.x branch, the 0.7.x branch will stay maintained for a while, but the 0.7.31 release will be the last one to contain new features. For anyone who does not depend on old D frontends, it is strongly recommended to switch to the 0.8.x branch as soon as possible and also to test with vibe-core (production deployments are safer off staying with the old :core module for now), as the transition period is supposed to be only as long as necessary to guarantee a stable implementation.

To give an overview, here is the list of the biggest changes:

- The whole library is now split into fully separate sub packages. This
  required some code changes, because there were some hidden circular
  dependencies between modules. Some parts have also been moved to the
  new sub packages "stream", "textfilter", "crypto" and "inet".

- Large parts of the API are now annotated with nothrow and @safe. In
  case of APIs that depend on callbacks, these can be breaking changes,
  but the most prominent places have deprecation paths in place.

- The vibe-d:core sub module has got a new configuration "vibe-core"
  that causes it to be replaced by the vibe-core package.

- The stream API has been made forward compatible with vibe-core. This
  adds optional IOMode parameters to the read/write methods (the value
  is currently ignored) and deprecates the leastSize and
  dataAvailableForRead properties.

The full change log for can be found at https://github.com/rejectedsoftware/vibe.d/blob/master/CHANGELOG.md

DUB pages:
http://code.dlang.org/packages/vibe-d/0.8.0-beta.1
http://code.dlang.org/packages/vibe-d/0.7.31-beta.1

[1]: https://github.com/vibe-d/vibe-core

On Tuesday, 31 January 2017 at 11:11:28 UTC, Sönke Ludwig wrote:
> For anyone who does not depend on old D frontends, it is strongly recommended to switch to the 0.8.x branch

What do you mean here by "old D frontends"? What are minimal dmd versions for 0.7 and 0.8 branches?

Am 31.01.2017 um 12:56 schrieb thedeemon:
> On Tuesday, 31 January 2017 at 11:11:28 UTC, Sönke Ludwig wrote:
>> For anyone who does not depend on old D frontends, it is strongly
>> recommended to switch to the 0.8.x branch
>
> What do you mean here by "old D frontends"? What are minimal dmd
> versions for 0.7 and 0.8 branches?

0.7.31 will work with 2.069-2.073 and 0.8.0 will work with 2.070-2.073. This is especially interesting because GDC master is still on 2.069.x.

On Tuesday, 31 January 2017 at 13:27:31 UTC, Sönke Ludwig wrote:

> 0.7.31 will work with 2.069-2.073 and 0.8.0 will work with 2.070-2.073. This is especially interesting because GDC master is still on 2.069.x.

Thanks!

On Tuesday, 31 January 2017 at 11:11:28 UTC, Sönke Ludwig wrote:
> The first release of the revamped core module [1] is nearing, and along with that, a compatible vibe.d release (0.8.0). The new core module is still opt-in in this release and can be activated using a `subConfiguration "vibe-d:core" "vibe-core"` directive in dub.sdl (`"subConfigurations": {"vibe-d:core": "vibe-core"}` in dub.json).
>
> [...]

Very nice!

Thanks for all your work on this - excellent stuff.

On Tuesday, 31 January 2017 at 11:11:28 UTC, Sönke Ludwig wrote:
>
> [1]: https://github.com/vibe-d/vibe-core

Is vibe-core still in alpha stage? Github page says so.

Am 31.01.2017 um 20:38 schrieb Arun Chandrasekaran:
> On Tuesday, 31 January 2017 at 11:11:28 UTC, Sönke Ludwig wrote:
>>
>> [1]: https://github.com/vibe-d/vibe-core
>
> Is vibe-core still in alpha stage? Github page says so.

It's de-facto beta stage, but I still need to add a beta tag and update the description. My hope was to get a little bit of practical feedback from others before the beta stage officially starts, but apart from possible cosmetics or small additions, the API is now finalized and all tests pass.

Am 31.01.2017 um 12:11 schrieb Sönke Ludwig:
> The first release of the revamped core module [1] is nearing, and along
> with that, a compatible vibe.d release (0.8.0). The new core module is
> still opt-in in this release and can be activated using a
> `subConfiguration "vibe-d:core" "vibe-core"` directive in dub.sdl
> (`"subConfigurations": {"vibe-d:core": "vibe-core"}` in dub.json).

Forgot to mention: Due to the way DUB currently handles "subConfigurations", an explicit dependency to "vibe-d:core" must also be present in the same package recipe, or it will silently do nothing. I'll try to improve this for the next release.

On Wednesday, 1 February 2017 at 09:35:02 UTC, Sönke Ludwig wrote:
> Am 31.01.2017 um 12:11 schrieb Sönke Ludwig:
>> The first release of the revamped core module [1] is nearing, and along
>> with that, a compatible vibe.d release (0.8.0). The new core module is
>> still opt-in in this release and can be activated using a
>> `subConfiguration "vibe-d:core" "vibe-core"` directive in dub.sdl
>> (`"subConfigurations": {"vibe-d:core": "vibe-core"}` in dub.json).
>
> Forgot to mention: Due to the way DUB currently handles "subConfigurations", an explicit dependency to "vibe-d:core" must also be present in the same package recipe, or it will silently do nothing. I'll try to improve this for the next release.

I don't understand what you mean. Will vibe-d:core be added as s dependency?

Am 01.02.2017 um 10:46 schrieb aberba:
> On Wednesday, 1 February 2017 at 09:35:02 UTC, Sönke Ludwig wrote:
>> Am 31.01.2017 um 12:11 schrieb Sönke Ludwig:
>>> The first release of the revamped core module [1] is nearing, and along
>>> with that, a compatible vibe.d release (0.8.0). The new core module is
>>> still opt-in in this release and can be activated using a
>>> `subConfiguration "vibe-d:core" "vibe-core"` directive in dub.sdl
>>> (`"subConfigurations": {"vibe-d:core": "vibe-core"}` in dub.json).
>>
>> Forgot to mention: Due to the way DUB currently handles
>> "subConfigurations", an explicit dependency to "vibe-d:core" must also
>> be present in the same package recipe, or it will silently do nothing.
>> I'll try to improve this for the next release.
>
> I don't understand what you mean. Will vibe-d:core be added as s
> dependency?

So you need to have both, subConfiguration(s) and dependenc(y/ies) in the package recipe, for example:

	name "foo"
	dependency "vibe-d:web" version="~>0.8.0-beta"
	// <- this would usually be the only dependency necessary,
	// but the following one is necessary so that subConfiguration
	// actually works:
	dependency "vibe-d:core" version="~>0.8.0-beta"
	subConfiguration "vibe-d:core" "vibe-core"