Thread overview
16th Planning
Dec 10, 2016
Martin Nowak
Dec 10, 2016
safety0ff
Dec 10, 2016
safety0ff
Dec 12, 2016
Martin Nowak
December 10, 2016
A few days too late, planning for the upcoming ~2.5 weeks (next planning on 2016-12-22, also see calendar [¹]).

Agenda:
- delaying 2.073?
- finish scope story
- CTFE update
- mangling abbreviations need feedback
- hopefully time for library array ops
- calendar
- <plese add your own>

====================

# delaying 2.073?

There are still a few issues I'd like to address in a 2.072.2 point
release, namely default-PIE on Ubuntu 16.10 and a few 2.071 regressions.
That hardly leaves time for a 2.073 beta before Christmas holidays.
Also we inherited plenty of bugs and 2 weeks delay from 2.072.0, so it's
a bit early for 2.073.
I'd propose to move the beta to CW 1 of 2017, with the release following
2 weeks later.

# finish scope story

We've lost plenty of time already, and there has been little progress on all the non-code work necessary to release this, phobos still doesn't build. Instead we entangle in long discussions on fundamental but tangential issues.

So let's please try to finish any remaining code issues, clarify outstanding questions, and getting the testing done. At best within the next 2 weeks, so we can get working on the non-code parts of the feature. As a reminder from last planning, non-code parts means documentation, changelog, an introductionary article, and at best an RC/Unique/WeakRef prototype library on dub.

Also created a scope branch for dlang.org
(https://github.com/dlang/dlang.org/tree/scope) to integrate docs for
the scope feature.
If changes to druntime or phobos become necessary (shouldn't), just
branch of a scope branch from master for those repos as well.
Please ask if anything is uncler.

I can take over the RC/Unique/WeakRef prototype once we have a somewhat working preview scope compiler (e.g. one that can compile phobos).

# CTFE

Just merged the first chunk of the CTFE work into the newCTFE feature
branch.
https://github.com/dlang/dmd/pull/6186
Stefan is steadily adding features. Will have another call in the next
few days to review (and merge) all the work from last month.

# mangling abbreviation

This is approaching a nice state.
https://github.com/dlang/dmd/pull/5855
Still need to get feedback from Iain Buclaw and Walter.

# library array ops

I my time permits, I'd want to finish the library array ops implementation. Not too realistic though.

https://trello.com/c/TNCQ6xBk/85-templated-library-arrayop-implementation-also-fixes-issue-15619-and-issue-16680

# public calendar

Just one comment, if you add dates, please make sure to include the exact meetup/user group/location/conference. Just a title of a talk is not that informative for a globally shared calendar ;).

If someone else is hosting D events, just let me know, or also become an admin on the calendar.

====================

That's about it from my side

December 10, 2016
On Saturday, 10 December 2016 at 06:34:52 UTC, Martin Nowak wrote:
> also see calendar [¹]).
>

What is the link for the calendar?

December 10, 2016
On Saturday, 10 December 2016 at 17:33:43 UTC, safety0ff wrote:
>
> What is the link for the calendar?

Found this one from the 15th planning thread:
https://calendar.google.com/calendar/embed?src=ut29n9vq9vu3ad4kbaabeed1d8%40group.calendar.google.com
December 12, 2016
On Saturday, 10 December 2016 at 17:52:45 UTC, safety0ff wrote:
> On Saturday, 10 December 2016 at 17:33:43 UTC, safety0ff wrote:
>>
>> What is the link for the calendar?
>
> Found this one from the 15th planning thread:
> https://calendar.google.com/calendar/embed?src=ut29n9vq9vu3ad4kbaabeed1d8%40group.calendar.google.com

Thanks for reposting that link, should also go somewhere in the wiki and on the website, if you happen to know good places for that.

==========

After a tiny bit of internal discussion, we moved the 2.073.0 release by about 1 month to mid Jan. Mainly to follow up with another 2.072.2 point release (date TBA) to address a few more regressions.

The calendar has been updated accordingly.

2017-01-04: 2.073.0-b1 (and branching)

https://github.com/dlang/dmd/milestone/14
https://github.com/dlang/druntime/milestone/12
https://github.com/dlang/phobos/milestone/11
https://github.com/dlang/dlang.org/milestone/12
https://github.com/dlang/installer/milestone/12
https://github.com/dlang/tools/milestone/8

2017-01-18: 2.073.0

https://github.com/dlang/dmd/milestone/13
https://github.com/dlang/druntime/milestone/11
https://github.com/dlang/phobos/milestone/10
https://github.com/dlang/dlang.org/milestone/11
https://github.com/dlang/installer/milestone/11
https://github.com/dlang/tools/milestone/7

Please tag any PR that MUST go into that release accordingly, and make sure to fully meet the dates with all parts that belong together.
MUST instead of SHOULD here means, that there are technical requirements for why a PR must be part of a release, or because a PR is a followup to something has already been merged and thus will be part of the release, e.g. a spec/website update for an already merged feature.

Be careful and don't rush for the departing train, the next one will follow suit.
I will bluntly ignore any wishes for still including feature X, Y, and Z.

2017-03-18 TBC: 2.074.0

https://github.com/dlang/dmd/milestone/15
https://github.com/dlang/druntime/milestone/13
https://github.com/dlang/phobos/milestone/12
https://github.com/dlang/dlang.org/milestone/13
https://github.com/dlang/installer/milestone/13
https://github.com/dlang/tools/milestone/9

-Martin

TBA => to be announced
TBC => to be confirmed