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
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).
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?
… 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.
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.
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.
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
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.
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).
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.
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 ), so I’m able to waive the waiting period and the extra votes needed (you have my reviewer +1 vote).