On 1/3/13 7:14 PM, Rob T wrote:
I have several times now pointed out in different threads that we have a *big* problem concerning the lack of a process for defining and implementing the D specification. It is very encouraging that we're now attempting to solve some big issues with the development and release process, but it only concerns the branching methods and movement of new code into a stable form. The next big ticket, which IMO is much more significant a change, is to define a process for managing the D specification in a more sensible way, in fact there is no process that I'm aware of, and if there is one it's totally dysfunctional.
Agreed.
At some point this problem has to be dealt with as it's a massive inhibitor for anyone to take D seriously. For example, try downloading the specification and you'll get http 404, or you get a link to some ancient crap from Amazon for .99 cents - seriously!
What's the link?
Try finding the most current version of the specification (there is no version to speak of). What's being proposed for the next big change? There's are DIPS, but where are they and how are they linked to the endless discussions surrounding them? Etc.
All good points.
I hope this major issue gets serious attention in the new year after 2.061 is released.
This looks like written from back in time. Yes it is getting attention, I hoped at least as much is obvious by now.
Andrei
