Thread overview | ||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
June 24, 2015 Beta D 2.068.0-b1 | ||||
---|---|---|---|---|
| ||||
First beta for the 2.068.0 release. http://downloads.dlang.org/pre-releases/2.x/2.068.0/ http://ftp.digitalmars.com/ Also available on Travis-CI as dmd-2.068.0-b1. A changelog containing all the upcoming changes will be provided within the next few days. Please report any bugs at https://issues.dlang.org -Martin |
June 24, 2015 Re: Beta D 2.068.0-b1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Martin Nowak | On Wednesday, 24 June 2015 at 23:14:05 UTC, Martin Nowak wrote:
> First beta for the 2.068.0 release.
There are 107 open pull requests in DMD, 32 in DRuntime, 78 in phobos, 25 in dlang.org, and a few elsewhere. I've seen a couple that are about 3 years old.
I kindly ask...
Contributuors:
* If you no longer wish to pursue your pull request, please close it
* If you do wish to pursue it please polish it up and rebase it so it has a chance
Reviwers & Committers:
* Please close any pull request that has a very low chance of getting merged (e.g. the PR has merge conflicts and the contributor is no longer active)
* If you see a pull request that has potential, but not for this release, please flag it with a "Post 2.068" tag, so we don't leave the contributor hanging.
* If you see a pull request that can still make it in 2.068, please make a final attempt at a review/merge so it is not delayed for yet another release.
Thanks,
Mike
|
June 25, 2015 Re: Beta D 2.068.0-b1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Martin Nowak | On Wednesday, 24 June 2015 at 23:14:05 UTC, Martin Nowak wrote: > First beta for the 2.068.0 release. > > http://downloads.dlang.org/pre-releases/2.x/2.068.0/ http://ftp.digitalmars.com/ > > Also available on Travis-CI as dmd-2.068.0-b1. > > A changelog containing all the upcoming changes will be provided within the next few days. > > Please report any bugs at https://issues.dlang.org > > -Martin Hi Martin, Would Summator be merged? https://github.com/D-Programming-Language/phobos/pull/2991 Ilya |
June 25, 2015 Re: Beta D 2.068.0-b1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Ilya Yaroshenko | On 25 June 2015 at 06:06, Ilya Yaroshenko via Digitalmars-d-announce <digitalmars-d-announce@puremagic.com> wrote: > On Wednesday, 24 June 2015 at 23:14:05 UTC, Martin Nowak wrote: >> >> First beta for the 2.068.0 release. >> >> http://downloads.dlang.org/pre-releases/2.x/2.068.0/ http://ftp.digitalmars.com/ >> >> Also available on Travis-CI as dmd-2.068.0-b1. >> >> A changelog containing all the upcoming changes will be provided within the next few days. >> >> Please report any bugs at https://issues.dlang.org >> >> -Martin > > > Hi Martin, > > Would Summator be merged? > More importantly, will all cross-platform regressions introduced in the development cycle of 2.068 be fixed? :-) |
June 25, 2015 Re: Beta D 2.068.0-b1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Mike | On Wednesday, 24 June 2015 at 23:59:43 UTC, Mike wrote: > * If you do wish to pursue it please polish it up and rebase it so it has a chance Which doesn't increase our review capacity, it would make more sense to only spent more effort on a pull on request. > * If you see a pull request that can still make it in 2.068, please make a final attempt at a review/merge so it is not delayed for yet another release. No, let's not play that game. Last minute additions are never a good idea and the next release is already coming in 2 month. I hope that more regular releases will help people to get their stuff ready in time. |
June 25, 2015 Re: Beta D 2.068.0-b1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Ilya Yaroshenko | On Thursday, 25 June 2015 at 04:06:15 UTC, Ilya Yaroshenko wrote:
> Would Summator be merged?
That sure looks useful, but I lack the time for a review and if it wasn't in master when we merged master into stable it won't be part of the release.
|
June 25, 2015 Re: Beta D 2.068.0-b1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Iain Buclaw | On Thursday, 25 June 2015 at 07:48:24 UTC, Iain Buclaw wrote:
> More importantly, will all cross-platform regressions introduced in the development cycle of 2.068 be fixed? :-)
Sure, we intend to fix all reported regressions.
|
June 25, 2015 Re: Beta D 2.068.0-b1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Martin Nowak | On Thursday, 25 June 2015 at 10:30:29 UTC, Martin Nowak wrote:
> On Wednesday, 24 June 2015 at 23:59:43 UTC, Mike wrote:
>> * If you do wish to pursue it please polish it up and rebase it so it has a chance
>
> Which doesn't increase our review capacity, it would make more sense to only spent more effort on a pull on request.
>
>> * If you see a pull request that can still make it in 2.068, please make a final attempt at a review/merge so it is not delayed for yet another release.
>
> No, let's not play that game. Last minute additions are never a good idea and the next release is already coming in 2 month.
> I hope that more regular releases will help people to get their stuff ready in time.
Then please flag things accordingly (milestone 2.068, post-2.068)
|
June 25, 2015 Re: Beta D 2.068.0-b1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Mike | On Thursday, 25 June 2015 at 10:42:46 UTC, Mike wrote:
>> No, let's not play that game. Last minute additions are never a good idea and the next release is already coming in 2 month.
>> I hope that more regular releases will help people to get their stuff ready in time.
>
> Then please flag things accordingly (milestone 2.068, post-2.068)
Martin, I see what you said here:
... if it wasn't in master when we merged master into stable it won't be part of the release.
I understand now. Please disregard my last statement.
|
June 25, 2015 Re: Beta D 2.068.0-b1 | ||||
---|---|---|---|---|
| ||||
Posted in reply to Martin Nowak | On 6/25/15 6:34 AM, Martin Nowak wrote:
> if it
> wasn't in master when we merged master into stable it won't be part of
> the release.
There is quite a raging debate currently happening with naming of lazy ranges that replace allocating ranges. If we blindly just accept what's currently in master, the debate is all for naught.
Should we wait until that is resolved, or should we simply end the debate and go with what happens to be in Master? Once those names are released, there's probably no chance to change them.
-Steve
|
Copyright © 1999-2021 by the D Language Foundation