On Tuesday, 13 January 2015 at 23:40:32 UTC, Martin Nowak wrote:
On Friday, 19 December 2014 at 16:45:40 UTC, Ola Fosheim
Grøstad wrote:
Yes, but it would be easy to define some focused goals for
each release and refuse to touch stuff that belongs to a later
release. E.g.
http://wiki.dlang.org/Agenda
That's a good start, but it is too vague. You need to design
ahead so that you don't start on the release without having
measurable goals and milestones. "c++ and gc" is not measurable.
You need to map out future releases and dependencies between
features.
Then you need to evaluate what went "wrong" in the last release,
and what was added to the last release, but not in the plan and
why. The "Agenda" is loosing its authority as a plan if it is not
evaluated. Without evaluation you can basically ignore it?
