January 08
On Wednesday, 3 January 2018 at 04:50:51 UTC, Martin Nowak wrote:
> We would still keep the bi-monthly releases, but make them point releases.
> So new additions could still be released regularly, but breaking changes and deprecations would have to wait until the next major release.

You probably mean minor releases. Point ones can only contain bug fixes and no features.


January 14
On Monday, 8 January 2018 at 06:21:05 UTC, Dicebot wrote:
> On Wednesday, 3 January 2018 at 04:50:51 UTC, Martin Nowak wrote:
>> We would still keep the bi-monthly releases, but make them point releases.
>> So new additions could still be released regularly, but breaking changes and deprecations would have to wait until the next major release.
>
> You probably mean minor releases. Point ones can only contain bug fixes and no features.

Yes, semver uses the less confusion terms MINOR (bi-monthly) and PATCH (bugfixes).
January 14
On 2018-01-14 20:04, Martin Nowak via Dlang-internal wrote:
> On Monday, 8 January 2018 at 06:21:05 UTC, Dicebot wrote:
>> On Wednesday, 3 January 2018 at 04:50:51 UTC, Martin Nowak wrote:
>>> We would still keep the bi-monthly releases, but make them point releases.
>>> So new additions could still be released regularly, but breaking changes and deprecations would have to wait until the next major release.
>> 
>> You probably mean minor releases. Point ones can only contain bug fixes and no features.
> 
> Yes, semver uses the less confusion terms MINOR (bi-monthly) and PATCH
> (bugfixes).

How would that work in terms of development?
Would we need another branch for deprecations and breaking changes?
Next ›   Last »
1 2 3