Jump to page: 1 2
Thread overview
Synchronize D 2.101.0 release with tooling please
Nov 14
ryuukk_
Nov 15
bauss
Nov 15
bauss
Nov 16
ryuukk_
Nov 16
bauss
Nov 16
Dennis
Nov 17
ryuukk_
Nov 17
M.M.
November 14

Please think about tooling before doing the release

As usual tooling was completely ignored

DUB merged stable without ImportC support.. [1]

  • DUB: needs ImportC support PR: [2]

  • DCD: needs to pick up bitfield support from recent libdparse PR [3]

So we can ensure users will have a great experience

[1] - https://github.com/dlang/dub/pull/2529

[2] - https://github.com/dlang/dub/pull/2522

[3] - https://github.com/dlang-community/libdparse/pull/476

November 15

On Monday, 14 November 2022 at 22:43:57 UTC, ryuukk_ wrote:

>

Please think about tooling before doing the release

As usual tooling was completely ignored

DUB merged stable without ImportC support.. [1]

  • DUB: needs ImportC support PR: [2]

  • DCD: needs to pick up bitfield support from recent libdparse PR [3]

So we can ensure users will have a great experience

[1] - https://github.com/dlang/dub/pull/2529

[2] - https://github.com/dlang/dub/pull/2522

[3] - https://github.com/dlang-community/libdparse/pull/476

I agree. No release should happen unless tooling is up to pair with the release.

November 15

On Tuesday, 15 November 2022 at 07:06:24 UTC, bauss wrote:

>

On Monday, 14 November 2022 at 22:43:57 UTC, ryuukk_ wrote:

>

Please think about tooling before doing the release

I agree. No release should happen unless tooling is up to pair with the release.

Could you list the tools that should have synchronized releases?

November 15

On Tuesday, 15 November 2022 at 09:10:54 UTC, Andrey Zherikov wrote:

>

On Tuesday, 15 November 2022 at 07:06:24 UTC, bauss wrote:

>

On Monday, 14 November 2022 at 22:43:57 UTC, ryuukk_ wrote:

>

Please think about tooling before doing the release

I agree. No release should happen unless tooling is up to pair with the release.

Could you list the tools that should have synchronized releases?

I would say the most important one would be dub.

November 16

On Monday, 14 November 2022 at 22:43:57 UTC, ryuukk_ wrote:

>

Please think about tooling before doing the release

As usual tooling was completely ignored

DUB merged stable without ImportC support.. [1]

  • DUB: needs ImportC support PR: [2]

  • DCD: needs to pick up bitfield support from recent libdparse PR [3]

So we can ensure users will have a great experience

[1] - https://github.com/dlang/dub/pull/2529

[2] - https://github.com/dlang/dub/pull/2522

[3] - https://github.com/dlang-community/libdparse/pull/476

New D version released, and this post got ignored, as expected

I guess folks have different priorities, that's unfortunate

November 16

On Wednesday, 16 November 2022 at 03:34:15 UTC, ryuukk_ wrote:

>

New D version released, and this post got ignored, as expected

No, it wasn't ignored. I think coordinating tooling with dmd releases is a good idea and plan to bring it to our next monthly meeting. There's just no way it could happen with this release through. The release process was already well underway when you posted this, and Iain Buclaw is managing it for the first time. It was a bit late and a bit much to throw on him at the last minute.

I'm highly confident I'll find general agreement on this in the meeting. Then it will just be a matter of identifying all of the tooling projects we need to keep in sync, who to coordinate with to make it happen, how to make it happen, etc. I see this as the sort of thing that would fall under the purview of the ecosystem management team once we get the ball rolling there.

November 16

On Wednesday, 16 November 2022 at 04:44:42 UTC, Mike Parker wrote:

>

On Wednesday, 16 November 2022 at 03:34:15 UTC, ryuukk_ wrote:

>

New D version released, and this post got ignored, as expected

No, it wasn't ignored. I think coordinating tooling with dmd releases is a good idea and plan to bring it to our next monthly meeting. There's just no way it could happen with this release through. The release process was already well underway when you posted this, and Iain Buclaw is managing it for the first time. It was a bit late and a bit much to throw on him at the last minute.

I'm highly confident I'll find general agreement on this in the meeting. Then it will just be a matter of identifying all of the tooling projects we need to keep in sync, who to coordinate with to make it happen, how to make it happen, etc. I see this as the sort of thing that would fall under the purview of the ecosystem management team once we get the ball rolling there.

I believe we should "synchronize" compiler release with essential packages (like vibe, mir, arsd-official etc) as well. I mean we should ensure that these packages won't break after compiler release.

This together with tooling will shape D managed ecosystem which I believe everyone will benefit from.

November 16
On 16/11/2022 7:24 PM, Andrey Zherikov wrote:
> I believe we should "synchronize" compiler release with essential packages (like vibe, mir, arsd-official etc) as well. I mean we should ensure that these packages won't break after compiler release.

They won't.

arsd is about the only project there that isn't tested on PR.

Adam is fairly conservative with a very large range of version support, so I'm fairly sure that is likely to not break.

https://buildkite.com/dlang/phobos/builds/7538

November 16
On Wednesday, 16 November 2022 at 06:38:35 UTC, rikki cattermole wrote:
> On 16/11/2022 7:24 PM, Andrey Zherikov wrote:
>> I believe we should "synchronize" compiler release with essential packages (like vibe, mir, arsd-official etc) as well. I mean we should ensure that these packages won't break after compiler release.
>
> They won't.
>
> arsd is about the only project there that isn't tested on PR.
>
> Adam is fairly conservative with a very large range of version support, so I'm fairly sure that is likely to not break.
>
> https://buildkite.com/dlang/phobos/builds/7538

I didn't see it. Glad we have this already.
November 16
On Wednesday, 16 November 2022 at 06:38:35 UTC, rikki cattermole wrote:
> arsd is about the only project there that isn't tested on PR.
>
> Adam is fairly conservative with a very large range of version support, so I'm fairly sure that is likely to not break.

New dmds do sometimes break my stuff though. This most recent one did due to a (random, unjustifed) Phobos change, but one of my users who used the beta dmd sent me an email, so I got a fix landed ahead of the formal release.

I have processes to test my stuff on old compilers, but not new ones. I rarely update stuff on my computers... so there is the risk that some dmd/phobos breakage will hit me.

But I can usually fix it pretty quick without regressing support for old compilers if someone lets me know.


« First   ‹ Prev
1 2