www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - Release D v2.076.1

reply Martin Nowak <code+news.digitalmars dawg.eu> writes:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Glad to announce D v2.076.1.

http://dlang.org/download.html

This point release fixes a few issues over v2.076.1, see the changelog
for more details.

http://dlang.org/changelog/v2.076.1.html

- -Martin
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEpzRNrTw0HqEtE8TmsnOBFhK7GTkFAlnb0ZcACgkQsnOBFhK7
GTlfQhAAtKFPULWZRcpnoBoZ3E5LOijGn3Xj5+08zyx2UZNt2qyZcBySK2rB6NRV
/GTn6fYUPI/tePBHVYACDhmILy8NcXIjdLy0eEdMdNlNfmNRqNZUUW1tKz4Ad6Y+
hwP2CrNYy0Rw8X/udmf8nGDB1Piu4ClJ1NzTDRGC6N1M419SSnErqv1l7gZITa9B
dqgbF4tgjNFHK9UTUcy744/vumoaq3aRsWoy0csytgCZd4n6Hk6BtwcQMmWzmXM5
YFbyLrqsnGDyBIoLYP180D6KKbtmlfjsmXEWouvZpGjyO/5XTlw0pG20TMe23AlZ
aqPRLJ5ysPVekpGi6Rl5MoEy2G5Ml7T1JTe/Grhrwh8ryivasX2NoX6/uB47gYSW
X3xHkfpDCp9GPUUiuH2DcdQkAP0TmGUDIKYbdXVySHDx6LMkVbEY43lHADU0bFru
C9CJMlBTd8RJWf7xl+w/8+4xHhm6yHjDq2+9wF/pcaqV7ifGH19dS3dATabXTEuO
aGESIc0siPnX47exVkV1qgH1UMAJ1odjsbEE0kgalu6cT/+eIs9R6BtBtoHNQnLq
Rgnd7easM6aL3S5a8KOfuj/47gRtrmr0+d59j3x1zIIxreEfQHyfO0x3Ho0raKK3
WvWVwwpusVm1Hg5xl+41lQjRAqqkhYmTiFnouDbgE0V0w+5cMag=
=+IlF
-----END PGP SIGNATURE-----
Oct 09
next sibling parent zabruk70 <sorry noem.ail> writes:
On Monday, 9 October 2017 at 19:44:24 UTC, Martin Nowak wrote:
 Glad to announce D v2.076.1.

 http://dlang.org/download.html

 This point release fixes a few issues over v2.076.1, see the 
 changelog for more details.

 http://dlang.org/changelog/v2.076.1.html

 - -Martin
http://dlang.org/changelog/v2.076.1.html - not found http://dlang.org/changelog/2.076.1.html - right url
Oct 09
prev sibling parent reply b4s1L3 <b2.temp gmx.com> writes:
On Monday, 9 October 2017 at 19:44:24 UTC, Martin Nowak wrote:
 Glad to announce D v2.076.1.

 http://dlang.org/download.html

 This point release fixes a few issues over v2.076.1, see the 
 changelog for more details.

 http://dlang.org/changelog/v2.076.1.html

 - -Martin
I didn't test the beta and missed this regression discovered by a CRON at TravisCI: https://issues.dlang.org/show_bug.cgi?id=17893
Oct 11
parent reply Petar Kirov [ZombineDev] <petar.p.kirov gmail.com> writes:
On Wednesday, 11 October 2017 at 10:20:01 UTC, b4s1L3 wrote:
 On Monday, 9 October 2017 at 19:44:24 UTC, Martin Nowak wrote:
 Glad to announce D v2.076.1.

 http://dlang.org/download.html

 This point release fixes a few issues over v2.076.1, see the 
 changelog for more details.

 http://dlang.org/changelog/v2.076.1.html

 - -Martin
I didn't test the beta and missed this regression discovered by a CRON at TravisCI: https://issues.dlang.org/show_bug.cgi?id=17893
Sound like we need more test coverage on the Project Tester (https://github.com/dlang/ci/blob/master/pipeline.groovy#L319).
Oct 11
parent reply b4s1L3 <b2.temp gmx.com> writes:
On Wednesday, 11 October 2017 at 13:08:38 UTC, Petar Kirov 
[ZombineDev] wrote:
 On Wednesday, 11 October 2017 at 10:20:01 UTC, b4s1L3 wrote:
 On Monday, 9 October 2017 at 19:44:24 UTC, Martin Nowak wrote:
 Glad to announce D v2.076.1.

 http://dlang.org/download.html

 This point release fixes a few issues over v2.076.1, see the 
 changelog for more details.

 http://dlang.org/changelog/v2.076.1.html

 - -Martin
I didn't test the beta and missed this regression discovered by a CRON at TravisCI: https://issues.dlang.org/show_bug.cgi?id=17893
Sound like we need more test coverage on the Project Tester (https://github.com/dlang/ci/blob/master/pipeline.groovy#L319).
The regression was discovered in iz, which was at least another time "victim" of a regression (almost day for day 1 year ago). https://github.com/BBasile/iz. This time it is trivial to overcome. It happens in a contract so checking for a version number does the job and the release version is not affected at all.
Oct 11
parent reply b4s1L3 <b2.temp gmx.com> writes:
On Wednesday, 11 October 2017 at 13:38:10 UTC, b4s1L3 wrote:
 On Wednesday, 11 October 2017 at 13:08:38 UTC, Petar Kirov 
 [ZombineDev] wrote:
 On Wednesday, 11 October 2017 at 10:20:01 UTC, b4s1L3 wrote:
 On Monday, 9 October 2017 at 19:44:24 UTC, Martin Nowak wrote:
 Glad to announce D v2.076.1.

 http://dlang.org/download.html

 This point release fixes a few issues over v2.076.1, see the 
 changelog for more details.

 http://dlang.org/changelog/v2.076.1.html

 - -Martin
I didn't test the beta and missed this regression discovered by a CRON at TravisCI: https://issues.dlang.org/show_bug.cgi?id=17893
Sound like we need more test coverage on the Project Tester (https://github.com/dlang/ci/blob/master/pipeline.groovy#L319).
The regression was discovered in iz, which was at least another time "victim" of a regression (almost day for day 1 year ago). https://github.com/BBasile/iz. This time it is trivial to overcome. It happens in a contract so checking for a version number does the job and the release version is not affected at all.
I can still add dmd beta as D Compiler in the CI. I think that iz occasionally breaks because it covers many programming style, not because of its "edginess", which means that's its probably not worth adding it to the Project tester.
Oct 12
parent reply b4s1L3 <b2.temp gmx.com> writes:
On Thursday, 12 October 2017 at 14:20:42 UTC, b4s1L3 wrote:
 On Wednesday, 11 October 2017 at 13:38:10 UTC, b4s1L3 wrote:
 On Wednesday, 11 October 2017 at 13:08:38 UTC, Petar Kirov 
 [ZombineDev] wrote:
 On Wednesday, 11 October 2017 at 10:20:01 UTC, b4s1L3 wrote:
 On Monday, 9 October 2017 at 19:44:24 UTC, Martin Nowak 
 wrote:
 Glad to announce D v2.076.1.

 http://dlang.org/download.html

 This point release fixes a few issues over v2.076.1, see 
 the changelog for more details.

 http://dlang.org/changelog/v2.076.1.html

 - -Martin
I didn't test the beta and missed this regression discovered by a CRON at TravisCI: https://issues.dlang.org/show_bug.cgi?id=17893
Sound like we need more test coverage on the Project Tester (https://github.com/dlang/ci/blob/master/pipeline.groovy#L319).
The regression was discovered in iz, which was at least another time "victim" of a regression (almost day for day 1 year ago). https://github.com/BBasile/iz. This time it is trivial to overcome. It happens in a contract so checking for a version number does the job and the release version is not affected at all.
I can still add dmd beta as D Compiler in the CI. I think that iz occasionally breaks because it covers many programming style, not because of its "edginess", which means that's its probably not worth adding it to the Project tester.
Also i'd like to say that the policy that is that regression fixes are commited on stable and that the fact that they only come to master in a "sync operation" is a problem. In the travis yaml we have to test dmd, dmd beta (stable, not yet released) and finally dmd master (current working tree). The policy should be changed so that regression fixes are commited to both master and stable, allowing to decrease the CI complexity. The problem is mainly that testing a project with dmd beta is pointless. It's only useful 1 or 2 weeks before a release, which happens , let's say, 4 times per years, leading to a waste of computing resources at the CI service. With reg fixes put in master at the same time that in stable, testing 3 versions of the DMD compiler would not be necessary anymore, i think.
Oct 12
parent reply Jonathan M Davis <newsgroup.d jmdavisprog.com> writes:
On Thursday, October 12, 2017 14:39:27 b4s1L3 via Digitalmars-d-announce 
wrote:
 Also i'd like to say that the policy that is that regression
 fixes are commited on stable and that the fact that they only
 come to master in a "sync operation" is a problem.

 In the travis yaml we have to test dmd, dmd beta (stable, not yet
 released) and finally dmd master (current working tree). The
 policy should be changed so that regression fixes are commited to
 both master and stable, allowing to decrease the CI complexity.

 The problem is mainly that testing a project with dmd beta is
 pointless. It's only useful 1 or 2 weeks before a release, which
 happens , let's say, 4 times per years, leading to a waste of
 computing resources at the CI service.

 With reg fixes put in master at the same time that in stable,
 testing 3 versions of the DMD compiler would not be necessary
 anymore, i think.
I don't know what the best way to handle committing regression fixes is, but I did find it annoying recently when I ran into a bug on master that I'd fixed on stable, but the fix hadn't been merged over yet. The fact that the fixes are delayed on master makes master buggier than it would be otherwise, and a number of us use master as our primary compiler. - Jonathan M Davis
Oct 12
parent Adam Wilson <flyboynw gmail.com> writes:
On 10/12/17 19:50, Jonathan M Davis wrote:
 On Thursday, October 12, 2017 14:39:27 b4s1L3 via Digitalmars-d-announce
 wrote:
 Also i'd like to say that the policy that is that regression
 fixes are commited on stable and that the fact that they only
 come to master in a "sync operation" is a problem.

 In the travis yaml we have to test dmd, dmd beta (stable, not yet
 released) and finally dmd master (current working tree). The
 policy should be changed so that regression fixes are commited to
 both master and stable, allowing to decrease the CI complexity.

 The problem is mainly that testing a project with dmd beta is
 pointless. It's only useful 1 or 2 weeks before a release, which
 happens , let's say, 4 times per years, leading to a waste of
 computing resources at the CI service.

 With reg fixes put in master at the same time that in stable,
 testing 3 versions of the DMD compiler would not be necessary
 anymore, i think.
I don't know what the best way to handle committing regression fixes is, but I did find it annoying recently when I ran into a bug on master that I'd fixed on stable, but the fix hadn't been merged over yet. The fact that the fixes are delayed on master makes master buggier than it would be otherwise, and a number of us use master as our primary compiler. - Jonathan M Davis
At work we branch out of stable (not yet released) and fix the bug. Merge branch to stable and then merge branch to master. Works pretty well. As long as you don't merge things into stable that you never intend for master. -- Adam Wilson IRC: LightBender import quiet.dlang.dev;
Oct 12