Track requests for dmd snap


#1

Snap name: dmd
Publisher: dlang

I’d like to request the following new tracks, in line with upstream releases since the package was last updated:

2.076
2.077
2.078

This reflects the package maintenance policy of trying to provide a track per upstream minor release, in accordance with earlier track requests: Track requests for dmd snap package


#2

Hello!

I have created these tracks for dmd based on Simplified track request process for snaps with predictable cadence since as a reviewer I’ve verified that the snap has existing tracks and the new requests conform to the previous ones, so I’m able to waive the waiting period and the extra votes needed (you have my reviewer +1 vote).

Cheers,

Daniel


#3

Thanks again, much appreciated :slight_smile:


#4

I’d like to request a new dmd track:

2.079

in order to handle the latest upcoming upstream release. Thanks in advance!


#5

Hello, I have created this track for dmd based on Simplified track request process for snaps with predictable cadence since as a reviewer I’ve verified that the snap has existing tracks and the new request conforms to the previous ones, so I’m able to waive the waiting period and the extra votes needed (you have my reviewer +1 vote). It can be used now.

However, I have a question. Initially we said dmd releases every ~3 months, but the last track request was less than a month ago! yikes! Is this because e.g. we created the track for 2.078 when that release was ~2 months old?

Let me know!

  • Daniel

#6

It’s because of me, not upstream – I had a busy period and so had a backlog of releases to package.

Last few upstream releases:
https://github.com/dlang/dmd/releases/tag/v2.076.0 (1 Sep 2017)
https://github.com/dlang/dmd/releases/tag/v2.077.0 (2 Nov 2017)
https://github.com/dlang/dmd/releases/tag/v2.078.0 (2 Jan 2018)

… and I’d anticipate the 2.079.0 release will be some time between the end of this week and the next.

So, it looks like they might have upped the cadence a bit to once every 2 months, not 3, but that could be just a short-term thing.

I can check in if you’re concerned about proliferation of tracks, but I don’t anticipate such a short turnaround for the next request.

By the way, thank you for the careful scrutiny on things like this (as for the ldc2 snap). I do appreciate it, as it helps me to regularly re-evaluate how I’m thinking about managing these packages.


#7

I’ve just confirmed with upstream that they now indeed have a 2-month release cadence. Here’s the plan for the upcoming year:
https://dlang.org/changelog/release-schedule.html

Let me know if that is going to be problematic w.r.t. tracks.


#8

Thanks for checking.

I don’t think it’s a problem, as long as the cadence is somewhat predictable and not like e.g. every week, and there are clear backward incompatibilities that necessitate keeping old releases (in tracks that users can opt into) around.


#9

I’d like to request one new track for dmd to handle the latest stable release:

2.080


#10

I’ve verified that the snap has existing tracks and the new request conforms to the previous ones, so I’m able to waive the waiting period and the extra votes needed (you have my reviewer +1 vote). Track 2.080 for dmd is ready and can be used now.


#11

I’d like to request a new track for dmd to handle the latest stable release:

2.081

Thanks and best wishes,

 -- Joe

#12

Wow this comes really close to the last track we created, 2.0.80 on May 30th. I’m hoping 2.0.81 is planned to be released near end of July to keep with the 2-month cadence we’d discussed :slight_smile:

Regardless, I’ve verified that the snap has existing tracks and the new request conforms to the previous ones, so I’m able to waive the waiting period and the extra votes needed (you have my reviewer +1 vote). Track 2.081 for dmd is ready and can be used now.


#13

That was me being late with the 2.080 release – it came out on 1 May:
https://dlang.org/changelog/2.080.0.html

… while 2.081 came out on 1 July:
https://dlang.org/changelog/2.081.0.html

… so their 2-month cadence is fine, it’s mine that’s a bit shaky :wink:

Anyway, thanks for creating the 2.081 track!


#14

I’d like to request some new tracks for dmd to handle the latest stable releases. Given the 2-month release cadence this means 3 new tracks:

2.082
2.083
2.084

(This is me catching up, as unfortunately in the last 6 months I wasn’t able to give the package the time it deserves…)

Thanks and best wishes,

-- Joe

#15

Hello!

I have created these tracks for dmd based on Simplified track request process for snaps with predictable cadence since as a reviewer I’ve verified that the snap has existing tracks and the new requests conform to the previous ones, so I’m able to waive the waiting period and the extra votes needed (you have my reviewer +1 vote).

Enjoy, Adam


#16

Hello again,

One more track request:

2.085

I know this comes hot on the heels of the last, but that’s due to the last request being late compared to the upstream releases – upstream has been on its regular 2 month minor release cadence (2.084 was 1 Jan 2019, 2.085 1 March 2019):
https://dlang.org/changelog/release-schedule.html

@ErnyTech has joined the maintenance team so please also allow him to make track requests in future.

Thanks and best wishes,

    -- Joe

#17

Hi again Joseph,

I have created the 2.085 track for dmd based as customary on Simplified track request process for snaps with predictable cadence since as a reviewer I’ve verified that the snap has existing tracks and the new requests conform to the previous ones (Joseph is what we’d call a frequent flyer and loyal customer :wink: ), so I’m able to waive the waiting period and the extra votes needed (you have my reviewer +1 vote).


#18

Hello,

As specified by the scheduled release calendar (https://dlang.org/changelog/release-schedule.html) we have released another version.

I would like to request another track for dmd:

  • 2.086

Thanks


#19

This is requested also from my side, if that makes a difference :slight_smile:


#20

Done, track 2.086 for dmd has been created in accordance with the customary process (my +1 as a reviewer, here for explicitness).

Cheers,

  • Daniel