On Tue, Oct 4, 2016 at 12:01 AM, Jack Applegame via Digitalmars-d-announce < digitalmars-d-announce@puremagic.com> wrote:

> On Thursday, 29 September 2016 at 13:44:53 UTC, Sönke Ludwig wrote:
>
>>
>> If no new issues come up, the 0.7.30 release is scheduled for the 9th of October.
>>
>> Please consider https://github.com/rejectedsoftware/vibe.d/issues/1583
>
>
Would it be okay for us to merge [0] as an example?

[0] https://github.com/rejectedsoftware/vibe.d/issues/1561

Am 31.08.2016 um 10:57 schrieb Sönke Ludwig:
> Main changes over 0.7.29:
>
>   - Compiles on the latest DMD version
>   - Added a new authorization framework for the web/REST interface
>     generators
>   - Extended the serialization framework with more hooks and traits,
>     enabling the use of custom UDAs - vibe-sdlang [1] is an SDLang
>     serialization module that became possible this way
>   - opDispatch has been removed from Bson/Json
>   - Optional support for using diet-ng [2] has been added (simply add it
>     as a dependency and it will be used by render())
>   - The HTTP client can now be used on Unix socket destinations
>   - Added table support for the Markdown compiler
>
> All changes:
> https://github.com/rejectedsoftware/vibe.d/blob/master/CHANGELOG.md
>
> DUB package:
> http://code.dlang.org/packages/vibe-d/0.7.30-beta.1
>
> [1]: http://code.dlang.org/packages/vibe-sdlang

Some more fixes: https://github.com/rejectedsoftware/vibe.d/commit/ab1ac33c564ad8d593104e30cc93eb1779c88d4a

Plus some regression fixes for issues that got introduced since the last alpha release (not mentioned in the change log).

The release has been rescheduled for next Thursday.

On Friday, 14 October 2016 at 19:57:09 UTC, Sönke Ludwig wrote:
> Am 31.08.2016 um 10:57 schrieb Sönke Ludwig:
>> Main changes over 0.7.29:
>>
>>   - Compiles on the latest DMD version
>>   - Added a new authorization framework for the web/REST interface
>>     generators
>>   - Extended the serialization framework with more hooks and traits,
>>     enabling the use of custom UDAs - vibe-sdlang [1] is an SDLang
>>     serialization module that became possible this way
>>   - opDispatch has been removed from Bson/Json
>>   - Optional support for using diet-ng [2] has been added (simply add it
>>     as a dependency and it will be used by render())
>>   - The HTTP client can now be used on Unix socket destinations
>>   - Added table support for the Markdown compiler
>>
>> All changes:
>> https://github.com/rejectedsoftware/vibe.d/blob/master/CHANGELOG.md
>>
>> DUB package:
>> http://code.dlang.org/packages/vibe-d/0.7.30-beta.1
>>
>> [1]: http://code.dlang.org/packages/vibe-sdlang
>
> Some more fixes: https://github.com/rejectedsoftware/vibe.d/commit/ab1ac33c564ad8d593104e30cc93eb1779c88d4a
>
> Plus some regression fixes for issues that got introduced since the last alpha release (not mentioned in the change log).
>
> The release has been rescheduled for next Thursday.

I guess you have a typo there:
"which used to be brokeb" you mean broken, right?

Am 14.10.2016 um 22:16 schrieb Namespace:
> I guess you have a typo there:
> "which used to be brokeb" you mean broken, right?

Right. I've fixed this and some others now. Thanks!

On Friday, 14 October 2016 at 19:57:09 UTC, Sönke Ludwig wrote:
> https://github.com/rejectedsoftware/vibe.d/commit/ab1ac33c564ad8d593104e30cc93eb1779c88d4a
>
> Plus some regression fixes for issues that got introduced since the last alpha release (not mentioned in the change log).
>
> The release has been rescheduled for next Thursday.

consider please https://github.com/rejectedsoftware/vibe.d/pull/1592

Am 15.10.2016 um 00:30 schrieb Jack Applegame:
> On Friday, 14 October 2016 at 19:57:09 UTC, Sönke Ludwig wrote:
>> https://github.com/rejectedsoftware/vibe.d/commit/ab1ac33c564ad8d593104e30cc93eb1779c88d4a
>>
>>
>> Plus some regression fixes for issues that got introduced since the
>> last alpha release (not mentioned in the change log).
>>
>> The release has been rescheduled for next Thursday.
>
> consider please https://github.com/rejectedsoftware/vibe.d/pull/1592
>

I need to think about the implications of each possibility (persistent, edge triggered, non-persistent, and non-persistent simulated) before the API gets changed. I'll do my best to comment on the PR tomorrow, but I can't promise that the change will still make it into this release (theoretically possible if it's clear that it won't cause any regressions). But even if not, it would of course be easy to put it on a branch or to tag an early pre-release version.